Sie sind auf Seite 1von 123

Support Handbook

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.


Support Handbook

Support Handbook
Remote Connectivity

Access to client test environment using Connectivity


TEMENOS strongly recommends connectivity between PACS and the client’s test system is available. This vastly reduces the time to
resolution especially for replication of problems. A briefing on what access permissions and restrictions must be in place is available
in later sections of this document.

Connectivity will be used only when the problem has been deemed as unable to replicate and hence requires an attempt to replication
in the client area. Connectivity for extracting information for issues returned to the client for more information is purely at the
discretion of PACS.

(Or)

In the area at Clients site i.e. either Test or Live by using tracers.

On-site or Access to test via Connectivity


There could be instances where further information is required in order to resolve a reported problem and in such cases TEMENOS
staff will need to access your system directly. Under no circumstances should any of your staff divulge T24 or system logins/passwords,
other than through the official procedure below. TEMENOS staff will not ask for them - all access by TEMENOS should be under your
control. To assist you in limiting this access we recommend the following access rights will need to be made available:

For straight access to T24


 A valid UNIX login and password, taking the user directly to the T24 sign on screen.
 A unique USER profile set up especially for the TEMENOS staff with:
 Ability to use all applications with S(ee), P(rint), L(ist) and E(xception) functions for the companies in use. Other functions
need be provided as required for the analysis of the issue.
 Applications with a program type of ‘W’ with additional I(nput) and V(erify) functions.
 Default settings from a USER.SMS.GROUP.
 Restricted connect time(s).

For access to universe / jBASE files


 A valid UNIX login and password, takes users directly to the universe / jBASE prompt.

This should be a different login name and password from that above in order for you to control access to your system.

Activate Passwords
Before the TEMENOS staff is expected or due to access your system:

 Set the passwords for Unix logins.


 Activate T24 USER profiles by using History restore.
 Change the password using PASSWORD.RESET.
 `If supervision is required, ensure your staffs are available.

When TEMENOS staff arrives or connect:

 Advise them of login names, passwords and system availability.


 Network logon procedures.
 Printers available for use.
 Any unique site instructions.

If a TEMENOS consultant is on-site, they will require use of a PC, printer and telephone.

2 PACS
Support Handbook

De-activate Password
When the TEMENOS staff leaves or disconnect:

 De-activate or change UNIX password.


 De-activate T24 USER profiles by reversing the records.

Contact Detail
Contact with any Front Office PACS can be made as follows:

PACS Switzerland PACS Singapore


Address Address
Chemin de Mancy 3 61 Robinson Road

CH - 1222 Vesenaz #20-01 Robinson Centre

Switzerland Singapore 068893

Phone +41 22 855 1655 Phone 1800 - 557 2877


Fax +41 22 855 1661 Fax 1800 - 557 2977
Email cshd@temenos.com Email sghelpdesk@temenos.com

PACS India PACS India


Address Address
146 Sterling Road KG 360*, M.G.R. Salai,

Nungambakkam Perungudi,

Chennai 600 034, India Chennai 600 096, India

Phone Phone +(91)(44) 4343 3000


+(91) (44) 6551 7701/2/3/5

Mobile +91 9176989837/38 Fax +(91) (44) 2822 2099


Skype cshd_temenos

Gtalk cshd.helpdesk@gmail.com

This information can also be found on the Temenos Website – www.temenos.com.

Contact Points
We request that each client nominate one central person for liaison with the PACS. This will ease any communication issues and
ensure that there is a consolidated view of the status of all outstanding problems agreed by both organisations.

This will avoid the situation where the PACS receives more than one call about the same problem from a number of different people
leading to confusion and delay in resolving the problem.

PACS Operations

PACS comprises the following entities


 Critical Call Centre
 PACS Back office
 Onsite PACS
 Regional Front office PACS

PACS is CMMI-CL3 certified and operates according to TQMS standards.

Critical Call Centre 24x7


 24x7 support for system down scenarios.
 Priority to get the system from a down state to running state

3 PACS
Support Handbook

 Primarily for COB support but also supports online failures.


 Clients are advised to call 24x7 only in case of a system shutdown situation. In such cases they are advised to “Call” 24x7 desk
(and not send mails) in order to avoid any loss of precious time that could result in Business hours loss. Please also use the
Instant Messenger facility as given in the PACS Contact Details for faster response.
 Onus of this team is to ensure that system is made available to the users without any loss of business.
 Handle calls related to T24 alone.

Back Office PACS


PACS Back office operates out of Chennai. The Chennai Back office operates from 9 AM IST to 9 PM IST between Monday – Friday
and between 11AM IST TO 8PM IST on Saturday and Sunday.

 The primary analysis wing of PACS that handles Live, Upgrading and Implementing clients, worldwide.
 Provides support for ‘Supported’ and ‘Un-Supported’ GLOBUS / T24releases and also bespoke releases (special workset).
 For upgrading clients, PACS supports the live and the upgrade area.
 Split into teams based on business streams
 Understand issues raised by client
 Advise the client if it is a setup issue
 Attempt to replicate the problem

First in the Demo area at the Back office after ensuring that the entire setup is similar to clients
environment based on the following criterion
• GLOBUS/T24 release

• Database, Oracle, Jbase

• Service Pack (SP) that the client is on

• Hot-fixes (or) T24 Updates that have been applied on top of the base release or SP

• Front-end application used – Desktop, GLOBUS Browser.

• Data feed simulators.

• Operating System

• Specific replication steps that are provided by the client

(Or)

In the clients area at Back office, if available either locally or through connectivity. Connectivity
will be used only when the problem has been deemed as unable to replicate and hence requires
an attempt to replication in the client area. Connectivity for extracting information for issues
returned to the client for more information is purely at the discretion of PACS.
(Or)

In the area at Clients site i.e. either Test or Live by using tracers.
Apparently, since so many steps are involved, delays are inevitable during replication especially if the issue is inconsistent.

 Post replication, code-analyse the problem


 Document the problem along with a suggestion for fix and pass the same to maintenance
 In case data base corrections are required by the client, provide the same

•With manual steps if the number of corrections are less

•With automated programs if the number of corrections are substantial.

In both cases we strongly advocate testing before the same is applied in the production system..

4 PACS
Support Handbook

When information is requested from the client and no response is received PACS will send
reminders in the following periodicity
The total wait period will be 15 calendar days, however there can be exceptions for a non responding client where the calendar will be
5 days.

We will break up the reminder time period as 3,3,2,2 to closure

For e.g.
Monday – Info requested from Client - 1 Jan 2006

Thursday – 1st reminder 3rd day (3 days) - 4 Jan 2006

Tuesday – 2nd Reminder 3rd day (3 days) - 9 Jan 2006

Thursday – 3rd Reminder 2nd day (2 days) - 11 Jan 2006

Monday – Closure Mail (2 days) - 16 Jan 2006

Onsite PACS
 PACS representation at the client place
 Carries source code of client release and locates the problem locally and suggest fix.
 Perform onsite analysis of core issues logged with PACS
 Pass replicated issues with code analysis to maintenance.
 Recommend fix
 Provide corrections in concurrence with PACS back office
 Quick turnaround of issues for critical clients who are upgrading, implementing or handling UAT.

Regional Front office PACS


 PACS instances at various other Temenos offices, similar to OSS.
 This team is not dedicated to any specific client and supports all clients in the area.
 Primary role is to do handle transient and sticky issues that do not replicate at Chennai.
 Pass corrections onsite where necessary.
 Carry source code with them and provide analysis of issues so as to enable fix.
 Perform preliminary analysis of issues logged with PACS
 Client follow up for information requests on returned issues

Maintenance
Any issue that is identified as a bug by PACS is subsequently fixed by our Maintenance team. Maintenance team is distributed across
our London, Chennai and Geneva offices. Once an issue is fixed Maintenance will provide a fix in the form of patch, service pack or
Update depending on the client release.

Support Manager
Single point of contact for the client, form the bridge between Client, PACS and Maintenance. SDMs prioritise issue analysis and fix
delivery based on the criticality of the problem as well as imminent client milestones. Provide regular feedback on status of issues to
client in the form of phone calls, mails and status reports.

5 PACS
Support Handbook

Contents
Support Handbook ........................................................................................................................................ 1
Support Handbook ........................................................................................................................................ 1
Account ....................................................................................................................................................... 11
Account Related Problems...................................................................................................................... 11
DISPO and POSTING.RESTRICT .......................................................................................................... 12
All in One Account (AZ) .............................................................................................................................. 13
ARC IB ........................................................................................................................................................ 13
ARC Mobile ................................................................................................................................................. 14
Arrangement Architecture ........................................................................................................................... 14
Asset Management ..................................................................................................................................... 15
Bills ............................................................................................................................................................. 19
Branch Resilience ....................................................................................................................................... 19
Cheque and Cards ...................................................................................................................................... 21
CARD and CHEQUES ISSUE ................................................................................................................ 21
Cheque.Collection ................................................................................................................................... 21
COLLATERAL............................................................................................................................................. 22
COLLATERAL - TAFC Compliance ........................................................................................................ 22
COLLATERAL - TAFJ Compliance ......................................................................................................... 23
CONFIRMATION MATCHING .................................................................................................................... 25
Customer & Accounts ................................................................................................................................. 26
Errors in CUSTOMER record .................................................................................................................. 26
Accounting overrides- Unauthorised, Available balance overdraft ......................................................... 26
Business Events ...................................................................................................................................... 29
CUSTOMER RELATIONSHIP MANAGEMENT ..................................................................................... 29
Enquiry STMT.ENT.BOOK Problem or balance problem ....................................................................... 29
EURO ...................................................................................................................................................... 30
INTEREST AND CHARGES ................................................................................................................... 31
LIMITS ..................................................................................................................................................... 32
Data ............................................................................................................................................................ 35
base ............................................................................................................................................................ 36
JEDI_FILEOP/READ_ERROR/WRITE_ERROR : ( External database) ................................................ 36
Oracle Driver licensing issues < No license installed for XMLORACLE driver> ..................................... 36
Oracle/Driver Related Issues .................................................................................................................. 36
XML-MSSQL/DB2 Database................................................................................................................... 38
XSD-Structured Storage ......................................................................................................................... 39
Delivery ....................................................................................................................................................... 40
DERIVATIVES ............................................................................................................................................ 45

6 PACS
Support Handbook

FATCA ........................................................................................................................................................ 46
FIDUCIARY................................................................................................................................................. 46
FOREIGN EXCHANGE .............................................................................................................................. 48
FORWARD RATE AGREEMENTS (FRA) .................................................................................................. 50
Front End .................................................................................................................................................... 51
Application works in telnet mode, but not in socket mode: ..................................................................... 51
Browser - TAFC Compliance .................................................................................................................. 51
Browser - TAFJ Compliance ................................................................................................................... 52
Browser connection issues - TAFC Compliance..................................................................................... 55
Browser connection issues - TAFJ Compliance ..................................................................................... 55
DESKTOP ............................................................................................................................................... 57
Desktop hanging ..................................................................................................................................... 57
Printing issues in Browser ....................................................................................................................... 57
T24 Web Services - TAFC Compliance .................................................................................................. 57
T24 Web Services - TAFJ Compliance ................................................................................................... 58
FUNDS.TRANSFER - TAFC Compliance .................................................................................................. 58
Guarantees ................................................................................................................................................. 61
LOANS AND DEPOSITS ............................................................................................................................ 62
MANAGEMENT INFORMATION SYSTEM (MIS) ...................................................................................... 63
Money Market ............................................................................................................................................. 63
Mortgages ................................................................................................................................................... 65
Mutual Funds .............................................................................................................................................. 66
NON-DELIVERABLE DEAL (ND) ............................................................................................................... 67
Nostro Reconciliation .................................................................................................................................. 67
PAYMENT DUES ....................................................................................................................................... 68
Payments .................................................................................................................................................... 69
DATA.CAPTURE .................................................................................................................................... 69
DIRECT DEBITS ..................................................................................................................................... 69
POSITION.MANAGEMENT ........................................................................................................................ 70
Process Workflow ....................................................................................................................................... 70
REPO (RP) ................................................................................................................................................. 71
Reporting .................................................................................................................................................... 72
Balance Mismatch ................................................................................................................................... 72
CAL CPL keys are not reported in CRF .................................................................................................. 72
GL differences ......................................................................................................................................... 73
Revaluation Errors / Currency differences .............................................................................................. 73
When there are no mismatches .............................................................................................................. 73
Entries not as expected ........................................................................................................................... 73

7 PACS
Support Handbook

Post Closing ............................................................................................................................................ 75


Securities .................................................................................................................................................... 76
CORPORATE ACTIONS ........................................................................................................................ 76
ET(EU SAVINGS DIRECTIVE) ............................................................................................................... 76
Securities ................................................................................................................................................. 77
Wealth Reporting (WR) ........................................................................................................................... 80
Wealth Reporting Orchestrate (WR-OR) ................................................................................................ 80
STANDING.ORDER ................................................................................................................................... 80
Structured Products .................................................................................................................................... 82
Syndicated Loans ....................................................................................................................................... 82
System Core ............................................................................................................................................... 85
System Core - TAFJ Compliance............................................................................................................ 85
ALTERNATE KEY issues - TAFC Compliance ....................................................................................... 85
ALTERNATE KEY issues - TAFJ Compliance ........................................................................................ 85
COB/EOD Error ....................................................................................................................................... 85
Constraints Processing - TAFC Compliance .......................................................................................... 88
Constraints Processing - TAFJ Compliance ........................................................................................... 89
DM related issues - TAFC Compliance ................................................................................................... 89
DM related issues - TAFJ Compliance ................................................................................................... 89
EB.DYNAMIC.ATTRIBUTES/EB.SWITCH.PARAMETER set up issues................................................ 89
EB.EOD.ERROR for Mismatch in Position and Consolidation ............................................................... 90
EB.TABLE.DEFINITION - TAFC Compliance ......................................................................................... 90
EB.TABLE.DEFINITION - TAFJ Compliance .......................................................................................... 90
Enquiries - TAFC Compliance................................................................................................................. 90
Enquiries - TAFJ Compliance ................................................................................................................. 91
Design Studio - TAFC Compliance ......................................................................................................... 91
Design Studio - TAFJ Compliance .......................................................................................................... 91
T24 Web Services ................................................................................................................................... 91
Integration Framework - TAFC Compliance ........................................................................................... 92
Integration Framework - TAFJ Compliance ............................................................................................ 92
Enquiry - TAFC Compliance ................................................................................................................... 93
Enquiry - TAFJ Compliance .................................................................................................................... 93
For access to universe / jBASE files ....................................................................................................... 93
For straight access to T24 ....................................................................................................................... 94
jBASE Issues........................................................................................................................................... 94
JUPORT issues ....................................................................................................................................... 97
NOFILE ENQUIRY .................................................................................................................................. 98
OFS Related Issues ................................................................................................................................ 98

8 PACS
Support Handbook

Problem in printing Deal slip / Enquiry report/ HOLD.CONTROL/ EB.TABLE.DEFINITION .................. 99


Run Time Errors ...................................................................................................................................... 99
SEAT ....................................................................................................................................................... 99
SMS ....................................................................................................................................................... 100
For problems related to SPF corruption - TAFC Compliance ............................................................... 100
For problems related to SPF corruption - TAFJ Compliance ................................................................ 101
System Tables - TAFC Compliance ...................................................................................................... 101
System Tables - TAFJ Compliance....................................................................................................... 102
TEMENOS CONNECTORS - TAFC Compliance ................................................................................. 103
TEMENOS CONNECTORS - TAFJ Compliance .................................................................................. 105
T-VERIFY .............................................................................................................................................. 107
Version .................................................................................................................................................. 107
T24 Administration .................................................................................................................................... 108
Activate Passwords ............................................................................................................................... 108
Archive Related Issues ......................................................................................................................... 108
Licensing Issue...................................................................................................................................... 108
Multi APP Server Architecture <Setup Queries> .................................................................................. 108
Multi-language problems - TAFC Compliance ...................................................................................... 109
Multi-language problems - TAFJ Compliance ....................................................................................... 109
Performance Issues .............................................................................................................................. 110
Printer Issues - TAFC Compliance........................................................................................................ 110
Printer Issues - TAFJ Compliance ........................................................................................................ 111
Processing Maintenance Code Requests ............................................................................................. 111
Product Installation Issues - TAFC Compliance ................................................................................... 111
Product Installation Issues - TAFJ Compliance .................................................................................... 111
STMT ENTRY ARCHIVE ...................................................................................................................... 112
Updates - TAFC Compliance ................................................................................................................ 112
Updates - TAFJ Compliance ................................................................................................................. 113
Upgrade Issues - TAFC Compliance .................................................................................................... 113
Upgrade Issues - TAFJ Compliance ..................................................................................................... 114
T24 Upgrade and Conversation................................................................................................................ 115
CONVERSION Issues - TAFC Compliance .......................................................................................... 115
CONVERSION Issues - TAFJ Compliance ........................................................................................... 115
Conversion related Problem <Jbase to Oracle using RDMB Conversion> .......................................... 115
TCIB & TCMB ........................................................................................................................................... 115
TCIB – Temenos Connect Internet Banking: ........................................................................................ 115
TCMB – Temenos Connect Mobile Banking ......................................................................................... 116
Teller ......................................................................................................................................................... 116

9 PACS
Support Handbook

Teller ..................................................................................................................................................... 116


TELLER FINANCIAL SERVICES.......................................................................................................... 116
Trade Finance ........................................................................................................................................... 118
SWAPS ..................................................................................................................................................... 120
EDGE ........................................................................................................................................................ 122
EDGE .................................................................................................................................................... 122
AML ........................................................................................................................................................... 123
ANTI MONEY LAUNDRY ...................................................................................................................... 123

10 PACS
Support Handbook

Account
Account Related Problems
Discrepancy in Account Balance

Incorrect Working Balance

Till R11 Release R12 Release

1. Full view of ACCOUNT S ZZZ 1. Full view of ACCOUNT S ZZZ


2. Full view of ACCOUNT.PARAMETER S SYSTEM 2. Full view of EB.CONTRACT.BALANCES S ZZZ
3. Output of ENQ STMT.ENT.BOOK WITH 3. Full view of ACCOUNT.PARAMETER S SYSTEM
BOOKING.DATE LE !TODAY
4. Output of ENQ STMT.ENT.BOOK WITH
4. Full view of EB.CONTRACT.BALANCES S ZZZ BOOKING.DATE LE !TODAY
5. Full view of transactions (if any) listed by below 5. Full view of transactions (if any) listed by above
command command
6. From jbase 6. From jbase

jsh-->SEARCH FXXX.ENTRY.HOLD jsh ~ -->SEARCH FXXX.ENTRY.HOLD

String :ZZZ String :ZZZ

String : String :

Record Keys : * Record Keys : *

>CT FXXX.ENTRY.HOLD >CT FXXX.ENTRY.HOLD

From jbase 7. From jbase

jsh ~ -->SEARCH FXXX.FWD.ENTRY.HOLD jsh ~ -->SEARCH FXXX.FWD.ENTRY.HOLD

String :ZZZ String :ZZZ

String : String :

Record Keys : * Record Keys : *

>CT FXXX.FWD.ENTRY.HOLD >CT FXXX.FWD.ENTRY.HOLD

Replace XXX with respective mnemonic of the company and ZZZ with problematic account number

Incorrect Actual or Cleared balance


Till R11 Release R12 Release

Full view of ACCOUNT Full view of ACCOUNT

Full view of ACCT.STMT.PRINT Full view of ACCT.STMT.PRINT

Full view of ACCOUNT.PARAMETER Full view of ACCOUNT.PARAMETER

Full view of EB.CONTRACT.BALANCES Full view of EB.CONTRACT.BALANCES

Full view of ACCT.ACTIVITY Full view of ACCT.ACTIVITY

from jBASE from jBASE

>TERM 400 >TERM 400

>SELECT FXXX.STMT.PRINTED WITH @ID LIKE "ZZZ..." >SELECT FXXX.STMT.PRINTED WITH @ID LIKE "ZZZ..."

>QSELECT FXXX.STMT.PRINTED >QSELECT FXXX.STMT.PRINTED

11 PACS
Support Handbook

>LIST FXXX.STMT.ENTRY TRANS.REFERENCE >LIST FXXX.STMT.ENTRY TRANS.REFERENCE


ACCOUNT.NUMBER BOOKING.DATE VALUE.DATE ACCOUNT.NUMBER BOOKING.DATE VALUE.DATE

EXPOSURE.DATE PROCESSING.DATE AMOUNT.LFCY EXPOSURE.DATE PROCESSING.DATE AMOUNT.LCY


AMOUNT.CY DATE.TIME SYSTEM.ID AMOUNT.FCY DATE.TIME SYSTEM.ID

Replace XXX with respective mnemonic of the company and ZZZ with problematic account number

DISPO and POSTING.RESTRICT


Posting restrict is not triggered for a transaction /In DISPO setup, after processing a transaction, DISPO.ITEMS record is not created
or if wrong DISPO.OFFICER is updated in DISPO.ITEMS record.

 Steps for replicating the problem along with screenshots.


 Full view of the problematic POSTING.RESTRICT record in SEE mode.
 Full view of the problematic ACCOUNT/CUSTOMER record in SEE mode where above POSTING.RESTRICT is attached.
 Full view of corresponding OVERRIDE record in SEE mode.
 Full view of corresponding DISPO.OFFICER record in SEE mode.
 Full view of corresponding DISPO.ITMES record in SEE mode.
 Full view of corresponding USER record who performed the transaction

12 PACS
Support Handbook

All in One Account (AZ)


Accounting problems in AZ
• AZ.PRODUCT.PARAMETER record.

• AZ.ACCOUNT record.

• AZ.SCHEDULES record.

• STMT.ENTRY records for all the transactions against the AZ.ACCOUNT

• Output of the ENQ STMT.ENT.BOOK for the AZ.ACCOUNT, NOMINATED and REPAY accounts where ever applicable.

• ACCOUNT.CREDIT.INT or ACCOUNT.DEBIT.INT for the applicable AZ records.

Balance mismatch in AZ
For balance mismatch, supply us with details of STMT.ENTRY, CATEG.ENTRY and RE.CONSOL.SPEC.ENTRY. (Refer to listing
mentioned in section 2.1 Balance Mismatch Messages of Chapter 2, Accounting and Reporting.) Along with the extraction of
RE.STAT.MISMATCH and RE.STAT.BAL.REC report on the same day, where listings are taken.

End of Day failures


● The specific job name and BATCH record name.
● A screen print of the error message.

Screen shots of the following.


● AZ.ACCOUNT
● AZ.SCHEDULES
● The system run date.
● Whether the system is a single or multi-company set-up.
● A full print of the COMO for the failed process.

ARC IB
For all the Archiving problems the following d etails need to be specified
● Detailed screenshot of the problem occurred along with the error message.
● The ARC IB browser war release and T24 release.
● Full view of AA.ARRANGEMENT.ACTIVITY record.
● If problem related to ENQUIRY, then full view of the ENQUIRY record.
● If problem related to VERSION, then full view of VERSION record.
● The arc ib war file release in which the problem exists.
● The global.log file (tcserver/log )
● Full view of AA.ARRANGEMENT.ACTIVITY record
● Full view of EB.EXTERNAL.USER record.

13 PACS
Support Handbook

ARC Mobile
1. T24 release – (example – R12, R13, etc.)

2. ARC Mobile release – (R13, R14, etc.)

3. Database used for ARC Mobile –(MySQL, Oracle, MSSQL server, etc.)

4. Application server used – (JBoss. Tomcat, etc..)

5. ARC Mobile server build details – (ARCMobile_executables_XX__X_XXXXXXXX_X.tar)

6. Handset Build details(if applicable) – (Mcommerce_iPhone_Prod_https-arcmobile-temenos-com-8080_24-03-2016.)

7. Whether reported issue happens in all platforms like IPhone, Android and Windows? If no, Specify which platform.

8. Steps to replicate (if applicable)– (1. Login android application, 2.Perform Fund transfer, 3. Transaction failed displaying “XYZ”)

9. Screenshots for the reported problem (if applicable)-

10. Application Server logs (if applicable)

Arrangement Architecture
For all the problems the following details need to be specified
● Detailed screenshot of the problem occurred along with the error message.
● Exact T24 release.
● Screen shot of AA overview screen
● Screen shot of all the arrangement conditions in case of tracking then product conditions.
● Screen shot of the product.
● Screen shot of EB.CONTRACT.BALANCES of the account
● Screen shot of the enquiry EB.CONTRACT.BALANCES.BALANCE
● Screen shot of the account record.
● Screen shot of ACCT.ACTIVITY record for R09 and below release
● Screen shot of ACCT.BALANCE.ACTIVITY record for R10 and above releases.
● Screen shot of AA.ACCOUNT.DETAILS record.
● Screen shot of AA.BILL.DETAILS record.
● Screen shot of AA.SCHEDULED.ACTIVITY record.
● Activity history (AA.ACTIVITY.HISTORY).
● All the product condition related to the product.
● API routines related to product condition.
● Arrangement overview record
● Activity log tab in full view.
● For activity related problems screen shot of the activity (i.e. AA.ARRANGEMENT.ACTIVITY).
● Schedules tab in full view.
● In case the problem is that the system is in an infinite loop then global.log

14 PACS
Support Handbook

● In case payment related problem like cash pool then setup of cash pool i.e. AC.CASH.POOL record and
other related setup.
● Further to that output of the enquiry STMT.ENT.BOOK for the debit account.
● Similarly in case of DD then DD.DDI, DD.ITEM,DD.PARAMETER and other related setup.

Asset Management
Provide records from the following files based on the functionality of the AM module where you face an issue. You need to provide
details which ever are relevant to the problematic scenario. Also ensure the details of the transactions underlying the position and
basic details like SECURITY.MASTER, SAM, and ACCOUNT are provided.

For issues related to AM Performance


● AM.PARAMETER
● SC.PARAMETER
● AM.PERF.PARAMETER
● SC.PERF.DETAIL
● RUN.PERFORMANCE.TAKEON and SC.PERF.DETAIL.MAN (If involved)
● TRANSACTION table
● TRANS.FUND.FLOW
● SC.FUND.FLOW
● SC.CASH.FLOW.TRANS
● AM.BREAKDOWN.SELECT
● Related SAM
● AM.FUND.FLOW
● AM.INST.VEH
● AM.INST.PERF.DETAIL
● AM.GROUP.PORT
● AM.PERF.DETAIL.GRP
● AM.EXCEPTION
● SC.POS.ASSET and SC.VALUATION.EXTRACT
● AM.INST.VEH.MAN, AM.INST.PERF.DETAIL.MAN (If involved)
● Time series enquiries AM.PERF.PRT.D.1M, AM.PERF.PRT.M, AM.PERF.PRT.4Q, AM.PERF.PRT.Y.10Y
● Core enquiries like AM.DAILY.PERF, AM.DIETZ.PERF
● Core enquiries AM.PERF.SEGMENT, AM.PERF.INSTRUMENT, AM.PERF.ROLLING,

For issues related to AM Valu ation Portfolio Consolidation


● AM.GROUP.PORT
● AM.GROUP.PORT.CONCAT
● AM.GROUP.PORT.CONCAT.LW

15 PACS
Support Handbook

● SC.POS.ASSET
● SC.VALUATION.EXTRACT
● SC.VALUATION.EXTRACT.LW
● AM.VALUATION.EXT.GRP.CONS
● AM.VALUATION.EXT.GRP.CONS.LW
● AM.PERF.DETAIL.GRP
● SC.PERF.DETAIL
● Underlying transactions creating the position
● COMO and TSA.SERVICE of service AM.GRP.PORT.ONLINE
● Core enquiries like AM.DAILY.PERF, AM.DIETZ.PERF

For issues related to AM Portfolio Modelling


● AM.PARAMETER
● AM.ENTITY
● Underlying SECURITY.MASTER, SAM
● AM.RATING
● INVESTMENT.PROGRAM
● AM.SIZING
● AM.AXIS
● AM.MATRIX
● AM.RECOMMENDATION
● AM.COMPARE
● AM.COMPARE.DETAIL
● AM.SCENARIO
● AM.PRICE.SET
● AM.BUILD.MODEL
● AM.MODEL
● AM.VIOLATION
● AM.GRID
● AM.LAST.COMPARE
● AM.GRID.FMT
● AM.POS
● AM.AXIS.MEMBER
● AM.MATRIX.HISTORY
● SEC.OPEN.ORDER, SC.SOO.CUST.DETAIL records

16 PACS
Support Handbook

● AM.SCENARIO.SAVED
● AM.CRITERIA
● AM.GRID.FMT.PARAM
● COMO and TSA.SERVICE of AM.SC.MOVEMENT service
● ENQUIRY output of AM.GRID.MASTER
● Enquiry output of AM.COMPARE.DETAILS (to display proposed orders)

For issues related to AM Dynamic modelling


● AM.PARAMETER
● SC.PARAMETER
● AM.VIRTUAL.CUSTOMER
● AM.VIRTUAL.ACCOUNT
● AM.DYNAMIC.MODEL
● AM.BUILD.MODEL
● AM.COMPARE
● SECURITY.MASTER
● AM.SEGMENTS
● AM.DYNAMIC.MODEL.COPY (if used)
● Related SC.PERF.DETAIL
● AM.MODEL.PORT.REBUILD records
● AM.AMEND.VIRTUAL.BALANCE
● COMO and TSA.SERVICE of service AM.MODEL.PORT.REBUILD
● COMO and TSA.SERVICE of service AM.DYNAMIC.MODEL.SERVICE
● COMO and TSA.SERVICE of service AM.MODEL.BUY.SELL.SERVICE
● For performance enquiries – output of AM.DYNAMIC.MODEL.PERF

For issues related to AM Restrictions


● AM.PARAMETER
● SC.PARAMETER
● AM.ENTITY
● RESTRICTION
● SC.SECURITY.CONSTRAINT
● SC.RESTRICTION.LOG
● Underlying CUSTOMER, SAM, SECURITY.MASTER, transactions

For issues related to AM cash management


● AM.PARAMETER

17 PACS
Support Handbook

● AM.SWEEP.REQUEST
● AM.SWEEP.DETAIL
● AM.LIQ.SWEEP.REQUEST
● AM.LIQ.SWEEP.DETAIL
● AM.CCY.HEDGE.REQUEST
● AM.CCY.HEDGE.DETAIL
● Core enquiries like AM.SWEEP.DETAIL.AMEND, AM.LIQ.SWEEP.DETAIL.AMEND,
AM.CCY.HEDGE.FORWARD.AMEND, AM.CCY.HEDGE.SWAP.AMEND

For issues related to AM Back Value Management


● AM.PARAMETER
● AM.VEH.MM and AM.VEH.GRP.MM
● Underlying transactions like SC.PRICE.CHANGE, AM.CCY.RATE, FT, DC, SEC.TRADE,
SECURITY.TRANSFER, POSITION.TRANSFER, SC.BOOK.COST, DIARY, ENTITLEMENT
● AM.INST.VEH, AM.INST.PERF.DETAIL, SC.CASH.FLOW.TRANS, SC.PERF.DETAIL
● ONLINE.BACKVALUE.LAUNCH
● BV.TRANSACTIONS and BV.COMP.TRANS
● AM.COMPOSITE
● AM.COMP.BV.UPD
● Batch record and relevant COMO of batch EOD.BACKVALUE
● Core enquiries AM.VAL.HIST, AM.VAL.GRP.HIST, BV.REPORT.LOG.SUMMARY, BV.PERF.REP

For issues related to AM XML Extractor


● SEC.ACC.MASTER
● AM.REP.PARAMETER
● AM.REPORT
● AM.EXTRACT.FQU
● AM.SUB.REPORT
● AM.REP.TEMPLATE
● XML.EXTRACTOR
● AM.PERF.PARAMETER
● Work files (AM.AC.STMT.WORKFILE, AM.ACT.WORKFILE, AM.PERF.WORKFILE,
AM.PERF.OVERVIEW.WORKFILE, AM.REP.CUSTOMERS)
● AM.REP.ONLINE
● AM.EXTRACT.HIST.LOG

For issues related to AM Front End Valuation


● AM.VAL.PARAMETER

18 PACS
Support Handbook

● CONFIG.ini
● Related AM.SEGMENTS, AM.ENTITTY, AM.AXIS
● Enquiry output of OS.SVG.MENU, GB.AM.SAM.INFO, AM.PORT.HOLDINGS, AM.PERF.PRT.D.1M,
GB.AM.CCY.GRID, GB.VALUATION.MATRIX, GB.VAL.CHART, GB.VAL.CHART.BAR,
GB.VAL.CHART.LINE, CASH.FLOW.PROJ, AM.SHARE.REPORT, AM.PERF.ROLLING,
AM.PERF.SEGMENT, AM.PERF.INST.SERIES, AM.PERF.D.1M.GRAPH, AM.PERF.PRT.M,
AM.PERF.PRT.4Q

Bills
Error message occurred during online:
● BL.BILL record
● BL.REGISTER record
● Screenshot of the error message

For all other BL problems


● BL.BILL
● BL.REGISTER
● BL.BALANCES
● EB.CONTRACT.BALANCES

Balance mismatch in BL
● For balance mismatch, supply us with details of STMT.ENTRY, CATEG.ENTRY and
RE.CONSOL.SPEC.ENTRY and EB.CONTRACT.BALANCES

Branch Resilience
For all the below problems the following details need to be specified
Whether the problem occurs in Classic/Browser Detailed screenshot of the problem occurred along with the error message

Problem in Static update:

Scenario: 1
If the problem is at Head office server provide us with the below information.

● BR.PARAMETER record.
● Provide us the entire folder and its contents from the location as specified in BR.PARAMETER.
● Also the screenshot of the STATIC update done at Head office.

Note: The static application are defined as per the bank’s requirement, the screenshot is required for the static application which
failed to update the OFS string in the path location as specified in BR.PARAMETER.

If the problem is at branch server provide us with the below information.

Provide us with the information requested in scenario: 1

● COMO of the service ran at branch server for static update.


● Screenshot showing the path where the STATIC file folder is FTP from the branch server.

19 PACS
Support Handbook

Problem in Account Update:

Scenario: 1
If the problem is at Head office server provide us with the below information.

● COMO of the service BR.EXPORT ran at head office.


● BR.PARAMETER record

Scenario: 2
If the problem occurred in Branch Server provide us with the below information.

Provide us with the information requested in scenario: 1

● COMO of the service ran at branch office server.


● Screenshot of the OFS.REQUEST.DETAIL for the problematic account record, if any.
Problem with date change in BRANCH office server

Provide records from the following files:

● COMO of the service BR.DATE.CHANGE from branch office server.


● HOLIDAY record of the local currency.
● DATES record for the respective company.
Problem with BR.CREATE.DATABASE

Provide records from the following files:

● COMO of the service BR.CREATE.DATABASE


● BR.PARAMETER record
● BR.BRANCH record
● BR.PRODUCT record

20 PACS
Support Handbook

Cheque and Cards


CARD and CHEQUES ISSUE
Card Issue problem
● CARD.CHARGE
● CARD.ISSUE
● CARD.TYPE
● ACCOUNT

Cheque Issue problem


● TELLER
● TELLER TRANSACTION
● PAYMENT.STOP
● CHEQUE.REGISTER.SUPPLEMENT
● ACCOUNT

Cheque.Collection
For all CHEQUE.COLLECTION related problem, provide us

● Full view of problematic CHEQUE.COLLECTION record


● Entries generated for the problematic CHEQUE.COLLECTION record (STMT AND CATEG ENTRIES)
● CQ.PARAMETER record
● Full view of Underlying TELLER transaction

21 PACS
Support Handbook

COLLATERAL
COLLATERAL - TAFC Compliance
For All Problems
● COLLATERAL
● COLLATERAL.RIGHT
● All Related LIMIT records

For R5 and Higher releases


For all problems related to LIMIT and COLLATERAL.

● LIMIT
● COLLATERAL
● COLLATERAL.RIGHT
● Full view of the LIMIT.COL.ALLOC.WORK record specified in the ALLOC.WORK.ID in the
corresponding LIMIT record

Discrepancy in the NOMINAL.VALUE of COLLATERAL record


● COLLATERAL and COLLATTERAL.RIGHT for the customer’
● Associated COLLATERAL.TYPE record
● Associated Application OR
● Associated Contract

COB HANG/CRASH IN COLLATERAL.RIGHT.EOD OR COLLATERAL.LIMIT.EOD


● mw42
● SHOW-ITEMS-LOCK
(A)

jsh-->TERM 300

jsh-->SEARCH FXXX.LIMIT.COL.ALLOC.WORK

String :<cust.no>

String :

Record Keys : *

>LIST FXXX.LIMIT.COL.ALLOC.WORK LIMIT.ID COLL.CODE COLL.RIGHT

(B)

jsh-->TERM 300

jsh-->LIST FXXX.LIMIT WITH @ID LIKE '...<cust.no>...' EXPIRY.DATE FIXED.VARIABLE COLLATERAL.CODE COLLAT.RIGHT
ALLOC.WORK.ID BY @ID

(C)

jsh-->TERM 300

jsh-->LIST FXXX.LIMIT$HIS WITH @ID LIKE '...<cust.no>...' EXPIRY.DATE FIXED.VARIABLE COLLATERAL.CODE


COLLAT.RIGHT ALLOC.WORK.ID BY @ID

22 PACS
Support Handbook

(D)

jsh-->TERM 300

jsh-->LIST FXXX.COLLATERAL.RIGHT WITH @ID LIKE '<cust.no>...' LIMIT.REFERENCE PERCENT.ALLOC LIMIT.ID


COLLATERAL.CODE STATUS EXPIRY.DATE ALLOC.WORK.ID BY @ID

(E)

jsh-->LIST-ITEM FXXX.LIMIT.LIABILITY WITH @ID LIKE '…<cust.no>...'

(F)

jsh-->LIST-ITEM FXXX.CUSTOMER.LIABILITY WITH @ID LIKE '…<cust.no>...'

(G)

jsh-->LIST-ITEM FXXX.LIMIT.LINES WITH @ID LIKE '…<cust.no>...'

Note: Replace XXX with company mnemonic.

Replace <cust.no> with customer id involved seen in the crash or hang or mw42 or show-item-locks

COLLATERAL - TAFJ Compliance


For All Problems
● COLLATERAL
● COLLATERAL.RIGHT
● All Related LIMIT records

For R5 and Higher releases


For all problems related to LIMIT and COLLATERAL.

● LIMIT
● COLLATERAL
● COLLATERAL.RIGHT
● Full view of the LIMIT.COL.ALLOC.WORK record specified in the ALLOC.WORK.ID in the
corresponding LIMIT record

Discrepancy in the NOMINAL.VALUE of COLLATERAL record


● COLLATERAL and COLLATTERAL.RIGHT for the customer’
● Associated COLLATERAL.TYPE record
● Associated Application OR
● Associated Contract

COB HANG/CRASH IN COLLATERAL.RIGHT.EOD OR COLLATERAL.LIMIT.EOD


 mw42
 SHOW-ITEMS-LOCK
 jsh-->LIST-ITEM FXXX.LIMIT WITH @ID LIKE '...<cust.no>...'
 jsh-->LIST-ITEM FXXX.LIMIT$HIS WITH @ID LIKE '...<cust.no>...'
 jsh-->LIST FXXX.COLLATERAL.RIGHT WITH @ID LIKE '<cust.no>...'
 jsh-->LIST-ITEM FXXX.LIMIT.LIABILITY WITH @ID LIKE '…<cust.no>...'
 jsh-->LIST-ITEM FXXX.CUSTOMER.LIABILITY WITH @ID LIKE '…<cust.no>...'

23 PACS
Support Handbook

 jsh-->LIST-ITEM FXXX.LIMIT.LINES WITH @ID LIKE '…<cust.no>...'

Note: Replace XXX with company mnemonic.

Replace <cust.no> with customer id involved seen in the crash or hang or mw42 or show-item-locks

24 PACS
Support Handbook

CONFIRMATION MATCHING
Problems related to Confirmation module:
 Error on formatting the CM messages.
 Set up issues in CM .MESSAGE.TYPE.
 Error on creating CM.HOLDING.QUEUE.
 Problem on creating CM.MESSAGE.
 Problem in CM.MATCH.ITEM record updation
 Swift message for which the tags has to be matched
 Problem on matching.

Files to be checked:
 >F.CARREIR.OUT.LIST.
 >F.CM.HOLDING.QUEUE
 >F.CM.MESSAGE.TYPE
 >F.CM.MATCH.ITEM
 >F.CM.MESSAGE
 >F.CM.MESSAGE.TYPE.MB

Phantoms for CM processing :


 In the lower releases up to R10 EB.PHANTOMs :
 EB.PHANTOM>CM.GET.NEW.MESSAGE - Updates CM.MATCH.ITEM AND CM.MESSAGE
 EB.PHANTOM>CM.FIND.MATCHED.ITEMS – Updates CM.PAR.UNMATCHED.ITEM AND CM.UNMATCHED.ITEM

From R11 the services:


1. BNK/CM.NEW.MESSAGE

2. BNK/CM.FIND.MATCH.MESSAGE

The MB phantom used in lower release is:


MB.CM.FIND.MATCHED.ITEMS

R11 service:

BNK/MB.CM.FIND.MATCH.MESSAGE

WORK FILES:
Two work files used in Confirmation Matching application are as follows:

 CM.UNMATCHED.ITEM : This file is used for full matching.


 CM.PAR.UNMATCHED.ITEM : This file is used for partial matching.

25 PACS
Support Handbook

Customer & Accounts


Errors in CUSTOMER record
1. Error Screenshot

2. Full view of CUSTOMER record if exists

3. Full view of VERSION through which customer is input

Accounting overrides- Unauthorised, Available balance overdraft


From Classic Prompt,

1. Full view of transaction with the override

2. Full view of ACCOUNT S ZZZ

3. Full view of latest ACCT.ACTIVITY

4. Full view of ACCT.STMT.PRINT S ZZZ

5. Full view of ACCOUNT.PARAMETER S SYSTEM

6. Full view of EB.CONTRACT.BALANCES S ZZZ

From jBASE Prompt,

>TERM 400

>SELECT FXXX.STMT.PRINTED WITH @ID LIKE "ZZZ..."

>QSELECT FXXX.STMT.PRINTED

>LIST FXXX.STMT.ENTRY TRANS.REFERENCE ACCOUNT.NUMBER BOOKING.DATE VALUE.DATE

EXPOSURE.DATE PROCESSING.DATE AMOUNT.LCY AMOUNT.FCY DATE.TIME SYSTEM.ID OVERRIDE

Replace XXX with respective mnemonic of the company and ZZZ with problematic account number

Account statement - formatting


1. Output of the statement generated

2. Full view of ACCOUNT.STATEMENT S ZZZ

3. Full view of DE.PARM S SYSTEM

4. Full view of respective PRINT.STATEMENT record

5. Full view of respective ENQUIRY record used in above PRINT.STATEMENT for statement format

6. Full view of respective REPORT.CONTROL record

7. Full view of DE.FORM.TYPE

8. Full view of the relevant DE.PRODUCT record

9. Full view of the relevant DE.CARRIER record

10. Full view of the relevant DE.ADDRESS record

Replace ZZZ with problematic account number

Sweeping
From Classic Prompt,

1. Full view of AC.ACCOUNT.LINK

2. Full view of AC.ACCOUNT.SWEEP.HIST

3. Full view of AC.SWEEP.TYPE

26 PACS
Support Handbook

4. Output of STMT.ENT.BOOK for the FROM and TO account

From jBase Prompt,

From jBASE

>TERM 400

>SELECT FXXX.STMT.PRINTED WITH @ID LIKE "ZZZ..."

>QSELECT FXXX.STMT.PRINTED

>LIST FXXX.STMT.ENTRY TRANS.REFERENCE ACCOUNT.NUMBER BOOKING.DATE VALUE.DATE

EXPOSURE.DATE PROCESSING.DATE AMOUNT.LCY AMOUNT.FCY DATE.TIME SYSTEM.ID

Replace XXX with respective mnemonic of the company and ZZZ with problematic account number

Cash Pooling
From Classic Prompt,

1. Full view of AC.CP.GROUP.PARAM

2. Full view of AC.SWEEP.TYPE

3. Full view of AC.CASH.POOL

4. Full view of AC.CASH.POOL.LINK

5. Full view of AC.ACCOUNT.SWEEP.HIST

6. Output of STMT.ENT.BOOK for the FROM and TO account

From jBase Prompt,

From jBASE

>TERM 400

>SELECT FXXX.STMT.PRINTED WITH @ID LIKE "ZZZ..."

>QSELECT FXXX.STMT.PRINTED

>LIST FXXX.STMT.ENTRY TRANS.REFERENCE ACCOUNT.NUMBER BOOKING.DATE VALUE.DATE

EXPOSURE.DATE PROCESSING.DATE AMOUNT.LCY AMOUNT.FCY DATE.TIME SYSTEM.ID

Replace XXX with respective mnemonic of the company and ZZZ with problematic account number

Account accrual mismatches


Section of the CRB report:

Verify RE.STAT.MISMATCH application on daily basis and check whether you have new mismatches. Extract the report from
&HOLD& file. This will have all the mismatches for that report.

Verify RE.STAT.BAL.REC application and provide us the same from &HOLD& file.

If we have mismatch in accrual (50000/51000/etc) key, then we have taken the following sample mismatch for analysis

Prior to R06

AC.1.TR.GBP.1003.3000.GG.205.No.50000 0.03 0.01 0.02

Information required based on the above mismatch

1.>TERM 300

>SELECT Fxxx.RE.CONSOL.ACCOUNT WITH @ID LIKE AC.1.TR.GBP.1003.3000.GG.205.No.INTCHG...

>QSELECT Fxxx.RE.CONSOL.ACCOUNT

>LIST Fxxx.ACCOUNT ACCR.CR.AMOUNT ACCR.CR2.AMOUNT ACCR.DR.AMOUNT ACCR.DR2.AMOUNT ACCR.CHG.CATEG


ACCR.CHG.SUSP ACCR.CR.SUSP ACCR.CR2.SUSP ACCR.DR.SUSP ACCR.DR2.SUSP

27 PACS
Support Handbook

2>TERM 300

>LIST Fxxx.ACCOUNT WITH CONSOL.KEY EQ AC.1.TR.GBP.1003.3000.GG.205.No ACCR.CR.AMOUNT ACCR.CR2.AMOUNT


ACCR.DR.AMOUNT ACCR.DR2.AMOUNT ACCR.CHG.CATEG ACCR.CHG.SUSP ACCR.CR.SUSP ACCR.CR2.SUSP ACCR.DR.SUSP
ACCR.DR2.SUSP

3> >TERM 300

> LIST FXXX.RE.CONSOL.SPEC.ENTRY WITH CONSOL.KEY.TYPE EQ “AC.1.TR.GBP.1003.3000.GG.205.No.50000” BY


TRANS.REFERENCE CURRENCY TRANS.REFERENCE BOOKING.DATE VALUE.DATE TOTAL AMOUNT.LCY TOTAL
AMOUNT.FCY TRANSACTION.CODE SYSTEM.ID COMPANY.CODE

Replace XXX with respective mnemonic of the company

In R06
AC.1.TR.GBP.1003.3000.GG.205.No.50000 0.03 0.01 0.02

Information required based on the above mismatch

1.>TERM 300

>SELECT Fxxx.RE.CONSOL.ACCOUNT WITH @ID LIKE AC.1.TR.GBP.1003.3000.GG.205.No.INTCHG...

>QSELECT Fxxx.RE.CONSOL.ACCOUNT

>LIST Fxxx.ACCOUNT ACCR.CR.AMOUNT ACCR.CR2.AMOUNT ACCR.DR.AMOUNT ACCR.DR2.AMOUNT ACCR.CHG.CATEG


ACCR.CHG.SUSP ACCR.CR.SUSP ACCR.CR2.SUSP ACCR.DR.SUSP ACCR.DR2.SUSP

2.>TERM 300

>SELECT Fxxx.RE.CONSOL.ACCOUNT WITH @ID LIKE AC.1.TR.GBP.1003.3000.GG.205.No.INTCHG...

>QSELECT FBNK.RE.CONSOL.ACCOUNT

>LIST FXXX.RE.CONTRACT.BALANCES CONSOL.KEY TYPE.SYSDATE OPEN.BALANCE CREDIT.MVMT DEBIT.MVMT


CURR.ASSET.TYPE OPEN.ASSET.TYPE

3.>TERM 300

>LIST FXXX.RE.CONTRACT.BALANCES WITH CONSOL.KEY EQ "AC.1.TR.GBP.1003.3000.GG.205.No" TYPE.SYSDATE


OPEN.BALANCE CREDIT.MVMT DEBIT.MVMT CURR.ASSET.TYPE OPEN.ASSET.TYPE

4.>TERM 300

> LIST FXXX.RE.CONSOL.SPEC.ENTRY WITH CONSOL.KEY.TYPE EQ “AC.1.TR.GBP.1003.3000.GG.205.No.50000” BY


TRANS.REFERENCE CURRENCY TRANS.REFERENCE BOOKING.DATE VALUE.DATE TOTAL AMOUNT.LCY TOTAL
AMOUNT.FCY TRANSACTION.CODE SYSTEM.ID COMPANY.CODE

Replace XXX with respective mnemonic of the company

R07 and above

AC.1.TR.GBP.1003.3000.GG.205.No.50000 0.03 0.01 0.02

Information required based on the above mismatch

1>TERM 300

>SELECT FXXX.RE.CONSOL.CONTRACT WITH @ID LIKE AC.1.TR.GBP.1003.3000.GG.205.No...

>QSELECT FXXX.RE.CONSOL.CONTRACT

>LIST FXXX.ACCOUNT ACCR.CR.AMOUNT ACCR.CR2.AMOUNT ACCR.DR.AMOUNT ACCR.DR2.AMOUNT ACCR.CHG.CATEG


ACCR.CHG.SUSP ACCR.CR.SUSP ACCR.CR2.SUSP ACCR.DR.SUSP ACCR.DR2.SUSP

2>TERM 300

>SELECT FXXX.RE.CONSOL.CONTRACT WITH @ID LIKE AC.1.TR.GBP.1003.3000.GG.205.No...

>QSELECT FXXX.RE.CONSOL.CONTRACT

>LIST FXXX.EB.CONTRACT.BALANCES CONSOL.KEY TYPE.SYSDATE OPEN.BALANCE CREDIT.MVMT DEBIT.MVMT


CURR.ASSET.TYPE OPEN.ASSET.TYPE

3>TERM 300

28 PACS
Support Handbook

>LIST FXXX.EB.CONTRACT.BALANCES WITH CONSOL.KEY EQ "AC.1.TR.GBP.1003.3000.GG.205.No" TYPE.SYSDATE


OPEN.BALANCE CREDIT.MVMT DEBIT.MVMT CURR.ASSET.TYPE OPEN.ASSET.TYPE

4>TERM 300

> LIST FXXX.RE.CONSOL.SPEC.ENTRY WITH CONSOL.KEY.TYPE EQ “AC.1.TR.GBP.1003.3000.GG.205.No.50000” BY


TRANS.REFERENCE CURRENCY TRANS.REFERENCE BOOKING.DATE VALUE.DATE TOTAL AMOUNT.LCY TOTAL
AMOUNT.FCY TRANSACTION.CODE SYSTEM.ID COMPANY.CODE

Replace XXX with respective mnemonic of the company

Business Events
● Full view of SPF and corresponding COMPANY record.
● Full view of ACCOUNT record and the transaction made.
● Full view of DEPT.ACCT.OFFICER record (of the above ACCOUNT record)
● Full view of attached corresponding EB.ALERT.REQUEST & the subscribed TEC.ITEMS record.
● Full view of generated F.EVENT.LOG and F.EVENT.LIST record
● Full view of delivery message generated from DE.O.HEADER
Output of below command from jsh prompt.

jsh-->jshow –c TEC.RECORD.EVENT

jsh-->jshow -c EB.CHECK.REDUNDANT.ALERT

CUSTOMER RELATIONSHIP MANAGEMENT


General information needed for initial analysis
● CR.CONTACT.LOG.PARAM
● CR.OPPORTUNITY.PARAMETER
● CUSTOMER record setup made in CUSTOMER.TYPE “Prospect” or “Active” CUSTOMER

The following screenshots to be provided as applicable to the problem scenario


● CR.OTHER.PRODUCTS
● CR.PROFILE.TYPE
● CR.CONTACT.LOG.
● CR.CONTACT.LOG.HIST
● CR.CONTACT.LOG.FUTR

Enquiry STMT.ENT.BOOK Problem or balance problem


From Classic Prompt,

● Full view of the ACCOUNT S ZZZ and its history records


● Full view of the ACCT.STMT.PRINT S ZZZ
● Full view of EB.CONTRACT.BALANCES S ZZZ
● Full view of the ACCOUNT.STATEMENT S ZZZ and its history records
● Full view of the latest ACCT.ACTIVITY record

29 PACS
Support Handbook

● Full view of ACCOUNT.PARAMETER S SYSTEM


● Full view of HOLIDAY and its history records
● Output of the Enquiry ENQ STMT.ENT.BOOK with ACCOUNT.NUMBER EQ ZZZ and BOOKING.DATE
with the relevant problematic date criteria
From the jBASE prompt,

a)

>TERM 300

>SSELECT FXXX.ACCT.ACTIVITY WITH @ID LIKE "ZZZ"

>LIST FXXX.ACCT.ACTIVITY DAY.NO TURNOVER.CREDIT TURNOVER.DEBIT BALANCE BK.DAY.NO BK.CREDIT.MVMT


BK.DEBIT.MVMT BK.BALANCE

b)

>TERM 300

>SELECT FXXX.STMT.PRINTED WITH @ID LIKE "ZZZ-..."

>QSELECT FXXX.STMT.PRINTED

>LIST FXXX.STMT.ENTRY BOOKING.DATE VALUE.DATE TOTAL AMOUNT.FCY TOTAL AMOUNT.LCY TRANS.REFERENCE


COMPANY.CODE DATE.TIME SYSTEM.ID

c)

>LIST.ITEM FXXX.STMT.PRINTED WITH @ID LIKE "ZZZ-..."

Replace XXX with respective mnemonic of the company and ZZZ with problematic account number

EURO
For all EU problems,

 SPF record
 Existing Local CURRENCY record and new local CURRENCY record
 EU.CONVERSION.PARAM record
 CURRENCY.PARAM record
 EU.PARAMETER record
 EB.SYSTEM.SUMMARY before and after conversion
 Output of ENQ EU.CONV.SUM

ACCOUNT conversion,

 EU.CCY.CONVERSION
 AC.CCY.CONVERSION
 ACCOUNT before and after conversion

CONTRACT conversion

 EU.CCY.CONVERSION
 EU.CONTRACT.CONVERSION
 Contract full view before and after conversion

30 PACS
Support Handbook

INTEREST AND CHARGES


Interest and charges problems

Interest Not Capitalized/Accrual not calculated:


> LIST F.SPF

> LIST F.EB.EOD.ERROR

> LIST F.BATCH LIKE ...SYSTEM.END.OF.DAY3...

> LIST FXXX.ACCOUNT EQ '<<ACCT.NUM>>'

> LIST FXXX.ACCR.ACCT.CR LIKE <<ACCT.NUM>>...

> LIST FXXX.ACCR.ACCT.DR LIKE <<ACCT.NUM>>...

> LIST FXXX.STMT.ACCT.CR LIKE <<ACCT.NUM>>...

> LIST FXXX.STMT.ACCT.DR LIKE <<ACCT.NUM>>...

> LIST FXXX.GROUP.CREDIT.INT LIKE <<COND.GRP>>...<<CCY>>...

> LIST FXXX.GROUP.DEBIT.INT LIKE <<COND.GRP>>...<<CCY>>...

> LIST FXXX.ACCOUNT.CREDIT.INT LIKE <<ACCT.NUM>>...

> LIST FXXX.ACCOUNT.DEBIT.INT LIKE <<ACCT.NUM>>...

> LIST FXXX.GROUP.CAPITALISATION LIKE <<COND.GRP>>...

> LIST FXXX.ACCT.CAPITALISATION LIKE <<ACCT.NUM>>...

> LIST FXXX.GROUP.ACCOUNT LIKE ...<<ACCT.NUM>>...

Note : Replace XXX with the problematic company mnemonic


Replace <<ACCT.NUM>> with the problematic ACCOUNT NUMBER
Replace <<COND.GRP>> with the CONDITION.GROUP of the problematic ACCOUNT
Replace <<CCY>> with the CURRENCY of the Problematic ACCOUNT

Charge not posted


> LIST F.SPF

> LIST F.COMPANY

> LIST F.ACCOUNT.PARAMETER

> LIST F.EB.EOD.ERROR

> LIST F.BATCH LIKE ...SYSTEM.END.OF.DAY3...

> LIST FXXX.ACCOUNT EQ '<<ACCT.NUM>>'

> LIST FXXX.STMT.ACCT.CH LIKE <<ACCT.NUM>>...

> LIST FXXX.GROUP.DEBIT.INT LIKE <<COND.GRP>>...<<CCY>>...

> LIST FXXX.ACCOUNT.DEBIT.INT LIKE <<ACCT.NUM>>...

> LIST FXXX.GENERAL.CHARGE LIKE <<CHG.CODE>>...

Note : Replace XXX with the Problematic company mnemonic


Replace <<ACCT.NUM>> with the ACCOUNT NUMBER of the problematic Account
Replace <<COND.GRP>> with the CONDITION.GROUP of the problematic ACCOUNT
Replace <<CCY>> with the CURRENCY of the Problematic ACCOUNT
Replace <<CHG.CODE>> with the value attached in the GEN.CHG.KEY attached in the ACCOUNT.DEBIT.INT/GROUP.DEBIT.INT

IC.COB performance
> LIST F.SPF

> LIST F.COMPANY

31 PACS
Support Handbook

> LIST F.ACCOUNT.PARAMETER

> LIST F.EB.EOD.ERROR

> LIST F.BATCH LIKE ...SYSTEM.END.OF.DAY3...

> LIST F.JOB.TIMES LIKE ...<<DATE>>...

> LIST F.PGM.FILE LIKE ...IC.COB...

Note : Replace <<DATE>> with the problematic date

LIMITS
For all Problems
Provide records from the following files:

 LIMIT for all the Limits in the group


 LIMIT.DAILY.OS, if available
 LIMIT.TXNS
 LIMIT.PARAMETER
 LIMIT.REFERENCE
 LIMIT.LIABILITY
 LIMIT.LINES

Discrepancy in the revaluation of LIMIT


HOLIDAY

Discrepancy in SECURED.AMT in LIMIT, when LIMIT is associated with COLLATERAL


 LIMIT (all limits related to the COLLATERAL.RIGHT)
 COLLATERAL.RIGHT
 COLLATERAL
 COLLATERAL.CODE
 COLLATERAL.TYPE
 Associated LIMIT.COL.ALLOC.WORK record. ID of this record can be taken from the field ALLOC.WORK.ID of LIMIT record
or COLLATERAL.RIGHT record.

Expired contracts in LIMIT.TXNS:


 LIMIT.TXNS
 Associated contracts
 History of Associated contracts.

Discrepancy between the value of TOTAL.OS in LIMIT and Forex outstanding amount
 FOREX
 LIMT.DAILY.OS

Discrepancy in the values of DATE.OF.EXCESS and DATE.1ST.EXCESS in LIMIT


record
 LIMIT
 ACCOUNT
 LIMIT.SUB.ALLOC
 ACCOUNT.OVERDRAWN (if entry exists)

32 PACS
Support Handbook

Problem in ENQ LIAB


 ENQ LIAB
 Drill down of ENQ LIAB
 LIMIT
 LIMIT.TXNS

Problem in ENQ CUSTOMER.POSITION


 ENQ CUSTOMER.POSITION
 ENQ CUSTOMER.POSITION.SUMMARY
 LIMIT
 Associated contract
 LIMIT
 ACCOUNT
 LIMIT.TXNS
 History records of ACCOUNT.
 History records of LIMIT.

COB CRASH / EB.EOD.ERROR - LIMIT.GET.ACC.BALS


 Account shown as missing in EB.EOD.ERROR
 Account history records
 Limit record associated with the Account
 LIMIT.TXNS
 LIMIT.LIABILITY
 LIMIT.LINES

COB CRASH / EB.EOD.ERROR IN ANY LIMIT/COLLATERAL jobs - TAFC Compliance


(A)

jsh-->TERM 300

jsh-->SEARCH FXXX.LIMIT.COL.ALLOC.WORK

String :<cust.no>

String :

Record Keys : *

>LIST FXXX.LIMIT.COL.ALLOC.WORK LIMIT.ID COLL.CODE COLL.RIGHT

(B)

jsh-->TERM 300

jsh-->LIST FXXX.LIMIT WITH @ID LIKE '...<cust.no>...' EXPIRY.DATE FIXED.VARIABLE COLLATERAL.CODE COLLAT.RIGHT
ALLOC.WORK.ID BY @ID

(C)

jsh-->TERM 300

jsh-->LIST FXXX.LIMIT$HIS WITH @ID LIKE '...<cust.no>...' EXPIRY.DATE FIXED.VARIABLE COLLATERAL.CODE


COLLAT.RIGHT ALLOC.WORK.ID BY @ID

(D)

jsh-->TERM 300

33 PACS
Support Handbook

jsh-->LIST FXXX.COLLATERAL.RIGHT WITH @ID LIKE '<cust.no>...' LIMIT.REFERENCE PERCENT.ALLOC LIMIT.ID


COLLATERAL.CODE STATUS EXPIRY.DATE ALLOC.WORK.ID BY @ID

(E)

jsh-->LIST-ITEM FXXX.LIMIT.LIABILITY WITH @ID LIKE '…<cust.no>...'

(F)

jsh-->LIST-ITEM FXXX.CUSTOMER.LIABILITY WITH @ID LIKE '…<cust.no>...'

(G)

jsh-->LIST-ITEM FXXX.LIMIT.LINES WITH @ID LIKE '…<cust.no>...'

Note: Replace XXX with company mnemonic.

Replace <cust.no> with customer id involved seen in the crash or hang.

COB CRASH / EB.EOD.ERROR IN ANY LIMIT/COLLATERAL jobs - TAFJ Compliance


 mw42
 SHOW-ITEMS-LOCK
 jsh-->LIST-ITEM FXXX.LIMIT WITH @ID LIKE '...<cust.no>...'
 jsh-->LIST-ITEM FXXX.LIMIT$HIS WITH @ID LIKE '...<cust.no>...'
 jsh-->LIST FXXX.COLLATERAL.RIGHT WITH @ID LIKE '<cust.no>...'
 jsh-->LIST-ITEM FXXX.LIMIT.LIABILITY WITH @ID LIKE '…<cust.no>...'
 jsh-->LIST-ITEM FXXX.CUSTOMER.LIABILITY WITH @ID LIKE '…<cust.no>...'
 jsh-->LIST-ITEM FXXX.LIMIT.LINES WITH @ID LIKE '…<cust.no>...'

Note: Replace XXX with company mnemonic.

Replace <cust.no> with customer id involved seen in the crash or hang or mw42 or show-item-locks

EB.EOD.ERROR - LIMIT.REVALUATION & LIMIT.CHECK


 LIMIT
 LIMIT.TXNS
 Associated contract

LIMIT MISM ATCH


 Full view of CONSOLIDATE.COND record with @ID ASSET&LIAB
 Full view of the SPF record.
 Full view of the LIMIT.PARAMETER record.
 Full view of the latest RE.STAT.MISMATCH reports.
 Full view of all the CAL records obtained by the below selection

CONSOLIDATE.ASST.LIAB

LL

0 LK ...<CAL ID>...

Output of below command from jshell prompt

a) jsh -> SELECT FXXX.RE.CONSOL.CONTRACT WITH @ID LIKE …<CAL ID>…

>QSELECT FXXX.RE.CONSOL.CONTRACT

>LIST FXXX.LIMIT

b) jsh->TERM 300

34 PACS
Support Handbook

c) jsh->LIST FXXX.EB.CONTRACT.BALANCES WITH CONSOL.KEY LIKE ...<CAL ID>... CONTRACT.BAL.ID CURRENCY


TYPE.SYSDATE VALUE.DATE MAT.DATE OPEN.BALANCE OPEN.BAL.LCL CREDIT.MVMT DEBIT.MVMT NAU.MVMT
NAU.TXN.ID CURR.ASSET.TYPE CO.CODE

d) jsh->LIST FXXX.RE.CONSOL.SPEC.ENTRY WITH CONSOL.KEY.TYPE LIKE ...<CAL ID>... DEAL.NUMBER AMOUNT.LCY


TRANSACTION.CODE CONSOL.KEY.TYPE CURRENCY AMOUNT.FCY EXCHANGE.RATE COMPANY.CODE

Data

35 PACS
Support Handbook

base
JEDI_FILEOP/READ_ERROR/WRITE_ERROR : ( External database)
 CT VOC F.XXX
 jstat –v F.XXX
 CT VOC STUBVIEW
 XMLdriver.log corresponding to error time stamp
 LIST STUBVIEW WITH @ID LIKE …TABLE.NAME… Where F.XXX is the problematic filename TABLE.NAME can be
obtained from the jstat output.
 Jshow –c EBS.CREATE.FILE
 Description of the table from SQL prompt as shown below SQL>DESC TABLE.NAME;
 Jsh->jdiag -dv

Oracle Driver licensing issues < No license installed for XMLORACLE


driver>
 jdiag –dvL (output in jdiag.out), run as root user only.
 jlicenseinfo –pt
 Copy of a JBASE_Form.doc < Which has sent to Distribution@temenos.com>

Oracle/Driver Related Issues


Information Required for All Issues
 The ‘ORAdriver.log’ created in the run directory.
 The COMO (if available) and/ or error message with the relevant timestamp.

jQL statement problems


 The output of the jQL query, from jshell prompt;
 The fresh ORAdriver.log file created after enabling ‘export JEDI_XMLORACLE_TRACE=1’
 The output of the relevant SQL statement (sql statement as obtained from ‘ORAdriver.log’);

COB Related issues


 Output of ORAdriver.log matching the time stamp of the COMO
 Output of COMO From the problematic tSA agent.

Problem related to Online like SELECT, LIST, KEY -SELECT etc


 Output of ORAdriver.log with the TRACE variable exported.
 Output of discrepant SELECT/LIST/KEY-SELECT output.

SQL statement problems found in ORAdriver.log


 Output of the same jQL statement from jshell prompt
 Output of ORAdriver.log for the matching time-stamp.
 Output of Execution of same SQL select output from Oracle end.

Problem during STANDARD.SELECT rebuild


 Output of the jshow on create-view
 Output of PGM.FILE entry for the specific application

36 PACS
Support Handbook

Performance problem on a SELECT.


 Output of existing Index from oracle level.
 Output of jshow on create-extindex from jshell.

Overall System performance


 Copy of Alert log file from the problematic database
 Copy of .profile from the problematic environment
 Output of Information on total Number of indexes existing in the T24 oracle database

Oracle driver setup problem (Setup issues)


 Output of jshow -c XMLORACLEInit
 Output of execution on config-file(XMLORACLE) from jshell
 Output of CT jedi_config from jshell

For the Oracle database locking in R11


 The install.sql script must be run. This now includes two new procedures T24_lock_request and T24_lock_release to handle
the locking. See under Configuration later for more details on this.
 The Oracle supplied script catblock.sql must have been run in the database by the DBA. This creates the Oracle DBA Lock
Views.
 The “execute” privilege on DBMS_LOCK must be granted to the T24 Oracle User.
 To complete this, do the following using the sqlplus command line tool:

sqlplus

sql> conn / as sysdba

sql> @$ORACLE_HOME/rdbms/admin/catblock.sql -- ($ORACLE_HOME/rdbms/admin is the default location for Oracle scripts)

sql> grant execute on dbms_lock to T24;

sql>quit

‘Oracle Not up’ problems


 Output of $lsnrctl from shell prompt
 Output of copy of ORAdriver.log <preferably tail -20>
 Output of search for the availability of DBA in a Bank

Total I/O Performance Issue

Functional Index present on a particular table


 Output of a Oracle indices on a particular table<should not go beyond 5 indices>
 Init.XXX.ora file from the problematic database

Multivalue support problems


 Output of jshow –c create-extindex
 Output of corresponding SQL from ORAdriver.log
 Output of driver release details which should support xmlexists() function and other XPath expressions

XML-Parsing Error on WIRTE


 Description of corresponding table from RDBMS
 Data Integrity check from the corresponding application team
 Check whether the data is out of xml boundary www.w3c.com standards

37 PACS
Support Handbook

SECURITY.VIOLATION/SPF corruption after migration from j4 to any RDBMS


 Copy of a .profile to check the Internationalization variables
 Confirmation on executing CONVERT.SYSTEM.UTF8.JBASE

Browser setup problem on RDBMS layer


 Copy of a .profile
 Copy of environment.vars and global.log from TCServer directory

Oracle/MSSQL/DB2 Index utilization problems


 Output of available indices for a particular table from rdbms
 Output of a corresponding dictionary to check a justification
 Output of a SELECT with EXPLAIN_PLAN variable enabled in .profile

JDLS Issues
Information Required for All Issues
 jDLS –dvL
 Server architecture

Locking failure scenario on JDLS


 Output a .profile from all the application server
 Resilience configuration available in profile

STUBLESS architecture

Locking problem
 Copy of a .profile from each UNIX accounts
 Output of JBASE_DATABASE from each application server

XML-MSSQL/DB2 Database
Compatibility Issues
 Output from client on RDBMS Server version/Driver Version/JBASE-T24 version details.

Database setup problems <SQL Server>


 Output of jedi_config from bnk.run directory
 Output of running ‘install.sql’ script from config-XMLMSSQL
 Output of Test table creation from SQL Server Management Studio
 Copy of .profile to check the minimal Environment variable as per Driver Release Notes

Database setup problems <DB2 Server>


 Output of jedi_config from bnk.run directory
 Output of db2 -finstall.sql -td@ -v from $DRIVER_HOME/sql
 Output of db2cli.ini
 Copy of .profile to check the minimal Environment variable as per Driver Release Notes

38 PACS
Support Handbook

XSD-Structured Storage
Implementation Issues
 Copy of ‘SCHEMA’ record from F.PGM.FILE.
 Description details of F_SCHEMA table from RDBMS.
 Screenshot of SS rebuild screenshot from T24 prompt.
 Copy of a .profile or jdiag -dvL information from the environment.

Schema Registration issues


 Output of CREATE-FILE using XSDSCHEMA qualifier option
 Output of problematic ORAdriver.log.

39 PACS
Support Handbook

Delivery
Service Errors:
 Formatting – SWIFT.OUT
 Swift Service – SWIFT.OUT
 Print Service – PRINT.OUT
 Inward formatting Service – SWIFT.IN

Phantom errors:
The error message when the particular phantom is run in INTERACTIVE mode.

 Mapping - DE.O.MAP.MESSAGES
 Formatting - DE.O.SELECT.NEXT.MESSAGE
 Swift phantom - DE.CC.GENERIC
 Print phantom - DE.O.CC.PRINT
 Inward formatting phantom - DE.I.SELECT.NEXT.MESSAGE

Messages going to the repair queue


Screen Dumps of the following records

 DE.MAPPING
 DE.MESSAGE
 DE.FORMAT.PRINT or DE.FORMAT.SWIFT
 DE.O.HEADER
 Outcome of the DE.O.HANDOFF record using ENQ DE.HANDOFF.DETS OR

In Database level run SEE.HANDOFF; enter Delivery key as for the DE.O.HEADER, e.g.

SEE.HANDOFF D2005020400005082700 – From R08 this feature is Obsolete.

From R08 and higher releases, you need to use the enquiry DE.HANDOFF.DETS to get the handoff information

SMS AND EM AIL Carriers


 DE.O.HEADER
 DE.FORMAT.XML
 From the jbase prompt,

The base XML schema file from F.DE.XML.SCHEMA ie T24Sms.xsd, T24Email.xsd

 F.DE.XML.SCHEMA for the corresponding DE.FORMAT.XML record


 Jdiag and .profile/remote.cmd from the area
 EB.TRANSFORM record
 Output of echo $CLASSPATH
 EB.API of DE.EMAIL.CLIENT and DE.SMS.CLIENT

Service errors
Unable to format error

R05

Run the formatting phantom DE.O.SELECT.NEXT.MESSAGE in the interactive mode and the error message

40 PACS
Support Handbook

Swift problem (interface)

1. Start the TSA.SERVICE XXX/DE.CC.GENERIC.IN or XXX/DE.CC.GENERIC.OUT in interactive mode and send us the screen shot
of the error message.

2. Batch record XXX/DE.CC.GENERIC.IN and XXX/DE.CC.GENERIC.OUT

3. TSA.SERVICE record XXX/DE.CC.GENERIC.IN and XXX/DE.CC.GENERIC.OUT

4. In case the problem is with incoming message, the actual incoming message

5. DE.INTERFACE records

Where XXX is the COMPANY Mnemonic

R06 and above


For both formatting and swift errors.

1. Start the service <Carrier>.IN and <Carrier>.OUT in interactive mode and the send us the screen shot of the error message

2. The full view of the BATCH record <Carrier>.IN and <Carrier>.OUT record

3. In case the problem is with inward, the actual incoming message

4. The DE.O.HEADER record

Discrepancy in the tag or value in the message:


Provide screen dumps of the following records

 DE.MESSAGE
 DE.FORMAT.PRINT or DE.FORMAT.SWIFT
 DE.O.HEADER
 Outcome of the DE.O.HANDOFF record using ENQ DE.HANDOFF.DETS OR
 In Database level run SEE.HANDOFF; enter Delivery key as for the DE.O.HEADER, e.g. SEE.HANDOFF
D2005020400005082700

Problem with incoming mes sages


 Provide screen dumps of the following records
 Incoming message processed
 DE.MESSAGE record
 Version attached
 The OFS.SOURCE record given in the DE.MESSAGE field
 OFS.RESPONSE.DETAIL for corresponding processing
 The VOC entry of the INWARD.OFS.RTN specified in the DE.MESSAGE record.

In case of Universe,

>CT VOC <>

In case of jBASE,

jshow–c <>

Source code of routine if its locally modified

In addition to the above for R06 and above for the errors where DE.I.HEADER and the F.SWIFT.IN.LIST not getting updated

 Tcserver.xml
 Global.log
 The BATCH and TSA.SERVICE records <Carrier.name>.IN

41 PACS
Support Handbook

Slow processing of messages


For releases below R06 :

File stat of the following files: (FILE.STAT for Universe and Jstat of JBASE)

 F.DE.O.HEADER
 F.DE.O.HANDOFF
 F.DE.O.PRI
 F.DE.O.PRI.ADVICE
 F.DE.O.MSG
 COMO of all the sessions for service DE.CC.GENERIC.OUT for release R05
 The full view of the DE.INTERFACE records and the routines

For releases R06 and above:

Jstat of the following files

 F.DE.O.HEADER
 F.DE.O.HANDOFF
 F.DE.O.PRI.<FORM.TYPE>
 The como from all sessions for the service <Carrier.name>.OUT
 The BATCH and TSA.SERVICE record <Carrier.name>.OUT
 The full view of the DE.INTERFACE records and the routines

For incoming (R06 and above):

For messages that has not reached T24

 Tcserver.xml
 Global.log

For messages that has reached T24

 The COMO of <Carrier.in> from all the sessions


 The full view of the related DE.INTERFACE records and its routines

DE.BIC Upload

DE.BIC.PARAMETER

DE.BIC.LOAD

Problem while running the Service XXX/DE.PRINT from R11 release onwards,

The DE.O.CC.PRINT phantom has been replaced with the multi-threaded service

TSA.SERVICE > XXX/DE.PRINT.

BATCH > BNK/DE.PRINT

DE.O.PRI.FORMS.SPOOL

DE.O.PRI.FORMS

MT942 Phantom to Service from R12 Onwards,

Similar to the Print phantoms only one record could be processed at a time with the DE.MT942.GENERATE phantom, leading to
performance problems.

The phantom is replaced with service DE.MT942.GENERATE to make the process multi-threaded. This makes the process scalable
and efficient.

Problem while formatting the Delivery message using the VRepair software from VIVEO ,

From R12 Release,

42 PACS
Support Handbook

T24 Delivery messages can now be processed with the VRepair software from VIVEO to convert non-standard SWIFT messages to
STP format.

The id of the parameter can be SYSTEM or COMPANY.CODE. This parameter can contain Message Type and Direction for each carrier
type

DE.STP.REPAIR.PARM

DE.STP.MSG.RESPONSE

DE.PARM

DE.O.HEADER

DE.INTERFACE

DE.MESSAGE

T24 EVENT ALERT generation problem,

There are two underlying parameter tables used for Event Definition: these are EB.EVENT.TYPE and

TEC.ITEMS.

EB.EVENT.TYPE

DE.CUSTOMER.PREFERENCE

EB.ALERT.REQUEST

ARCHIVAL ERROR:

Outward:

Service >DE.EOP.OUTWARD

Report>DE.PRODUCE.AWACK.REPORT

Files to checked and archived:


F.DE.O.HEADER

F.DE.O.MSG

F.DE.PARM

F.DE.O.AWAK

F.DE.O.STATISTICS

F.DE.STATISTICS

F.DE.AWAK.WRK

If history details are to be maintained, the open the files F.DE.O.HISTORY.QUEUE and F.DE.O.HEADER.ARCH

Inward:
Service >DE.EOP.INWARD

Files to checked and archived:


F.DE.I.HEADER

F.DE.I.MSG

F.DE.PARM

F.DE.I.STATISTICS

F.DE.STATISTICS

F.DE.MSG.AUDIT

If history details are to be maintained, then open files F.DE.I.HEADER.ARCH and F.DE.I.HISTORY.QUEUE

43 PACS
Support Handbook

T24.PAYMENTS.INFO
The tool T24.PAYMENTS.INFO can be used to extract delivery related files for both inward and outward delivery processing.

The tool and the user guide is available in the link https://tcsp.temenos.com/Pages/ToolsnUtil.aspx

Files extracted using the tool:

DE.I.HEADER/DE.O.HEADER

ENQ OUTPUT OF DE.HANDOFF.DETS

DE.MESSAGE

VERSION/OFS.SOURCE attached in DE.MESSAGE

DE.MAPPING

DE.CARRIER

DE.PRODUCT

DE.ADDRESS

DE.INTERFACE

DE.FORMAT.SWIFT/DE.FORMAT.PRINT/DE.FORMAT.XML

DE.FORM.TYPE

EB.TRANSFORM

DE.XML.SCHEMA

CLASSPATH

VERSION/OFS.SOURCE/ROUTINE attached in DE.MESSAGE

FT ID AND OFS.REQUEST.DETAIL for inward processing

jshow of routines attached in DE.INTERFACE/DE.MAPPING/DE.MESSAGE

ACTIVITATION FILE

DE.O.MSG.<CARRIER>

DE.O.MSG.<FORM.TYPE>

DE.O.HISTORY/ DE.I.HISTORY

DE.I.MSG.<CARRIER>

44 PACS
Support Handbook

DERIVATIVES
Provide records from following files:

 DX.TRADE
 DX.TRANSACTION
 DX.PARAMETER
 DX.CONTRACT.MASTER
 DX.REP.POSITION
 DX.MARKET.PRICE

Issues related to IM or VM
 DX.COB.WORKFILE record for the problematic –‘customer/exchange’
 COMO file of the DX.RV.SERVICE, if the client is using the online SERVICE for performing the DX revaluation process or
else the COMO of the batch job DX.COB.REVALUE (in batch DX.END.OF.DAY) needs to be provided
 DX.MARKET.PRICE
 All STMT.ENTRY related to IM or VM

Issues related to CAL or imbalance


 DX.TRANS.BALANCES
 RE.CONTRACT.BALANCES
 CRD and TRANS.JOURNAL reports.
 Screen shot of CAL
 Related STMT.ENTRY, CATEG.ENTRY AND RE.CONSOL.SPEC.ENTRY

Issues related to DX POSITION


 DX.REP.POSITION
 DX.TRANSACTION for the respective position key.

Issues related to closeout


 Screen shots of DX.CLOSEOUT
 All DX.TRANSACTION records related to the problematic DX.TRADE
 Related to the DX.REP.POSITION

DX Online issue
 DX.TRADE
 Related DX.TRANS.KEYS
 Related DX.TRANSACTION
 Related Its DX.REP.POSTION
 Related STMT.ENTRY

DX COB crash related issues


 Full view of COMO files for all the Cob agents.
 Full view ORA driver.log file (If Database is ORACLE)
 Oracle Alert log file. (if Database is ORACLE)
 EB.EOD.ERROR
 jstat output, if the problem in the specific T24 file with WRITE/READ error.

45 PACS
Support Handbook

FATCA
For all FATCA related problems

 Full view of corresponding FATCA.CUSTOMER.SUPPLEMENTARY &


 Full view of FATCA.TAX.BASE
 Full view of FATCA.REPORTING.PARAMETER
 Full view of FATCA.PARAMETER

FATCA.TAX.BASE not updated

 Full view of corresponding FATCA.CUSTOMER.SUPPLEMENTARY


 Full view of FATCA.TAX.BASE if present
 Full view of FATCA.REPORTING.PARAMETER
 Full view of FATCA.PARAMETER

FATCA.STATUS not updated as expected or not marked as RECALCITRANT/DORMANT

 Full view of corresponding FATCA.CUSTOMER.SUPPLEMENTARY


 Full view of FATCA.STATUS.CONDITION
 Full view of FATCA.REPORTING.PARAMETER
 Full view of FATCA.PARAMETER

FATCA XML file not generated

 Full view FATCA.XML.REQUEST


 Full view of FATCA.REPORTING.PARAMETER
 Full view of FATCA.PARAMETER
 From jshell
 >LIST FBNK.FATCA.TAX.BASE FATCA.STATUS
 >LIST FBNK.FATCA.AGGR.TAX.BASE FATCA.STATUS

Expected customer not reported in XML file

 Full view of corresponding FATCA.CUSTOMER.SUPPLEMENTARY


 Full view of FATCA.REPORTING.PARAMETER
 Full view of FATCA.PARAMETER
 XML file

Error during XML file validation

 Error screenshot
 Full view of FATCA.REPORTING.PARAMETER
 Full view of FATCA.PARAMETER
 XML file

FIDUCIARY
 FD.FID.ORDER record
 FD.FIDUCIARY record
 FD.BALANCES records for both order and placement
 FD.GROUP.PAYMENT record
 FD.POOL.GROUP record
 FD.PARAMETER record

46 PACS
Support Handbook

Balance mismatch in FD
Balance mismatch in FD .For balance mismatch, supply us with details of STMT.ENTRY, CATEG.ENTRY and
RE.CONSOL.SPEC.ENTRY. Also , please provide RE.STAT.MISMATCH and RE.STAT.BAL.REC report on the same day, where
listings are taken.

47 PACS
Support Handbook

FOREIGN EXCHANGE
Provide records from the following files:

FOREX
FX.TRANSACTION.TYPE

FX.PARAMETERS

If the problem is related to :

1) Online field level problems or Mis calculations.

a) Send the sequence of Input

b) If the problem is specific to Browser send the details requested in Browser chapter

2) Accounting error/ mismatches then send the

a) TRANS.JOURNAL (TRANS.JOURNAL2 –Prior to R8 / TXN.JOURNAL.PRINT – From R8) for the respective date

b) All the accounting entries for the problematic contract.

c) RE.CONSOL.FOREX (for releases lesser than R08) / EB.CONTRACT.BALANCES (for releases above R08)

d) Full view of the CONSOLIDATE.ASST.LIAB record

e) RE.STAT.MISMATCH and RE.STAT.BAL.REC reports

3) Problem in the maturity of the contract, then

a) COMO of BATCH FX.END.OF.DAY for the respective maturity date, if SOD.MAT is set as YES in the contract then provide
the COMO of BATCH FX.START.OF.DAY.

b) If it is SPLIT month end Maturity, then HOLIDAY records

4) Online FATAL.ERROR on LIMIT related (either while input, amend, reversal), then LIMIT.TXNS and LIMIT.DAILY.OS of the
respective contract and the LIMIT.PARAMETER record

5) Position & Revaluation related, then

a) Corresponding POSITION and POS.TRANSACTION records.

b) Outcome of FX.POSITIONS and REVALUATION reports from the HOLD.CONTROL.

c) POS.MVMT.HIST listings for the problematic contract

d) REVALUATION.PARAMETER record to know on which method the revaluation was setup.

e) All the accounting entries for the problematic contract.

f) LATEST EB.SYSTEM.SUMMARY record; and EB.SYSTEM.SUMMARY. EB.JOURNAL.SUMMARY listing

6) Delivery related, then

a) DE.MESSAGE, DE.MAPPING, DE.FORMAT.SWIFT of the related MTnnn (300, 103, 202 etc…) message

b) Outcome of the DE.O.HANDOFF record using ENQ DE.HANDOFF.DETS OR

c) In Database level run SEE.HANDOFF; enter Delivery key as for the DE.O.HEADER, e.g. SEE.HANDOFF
D2005020400005082700

d) HOLIDAY records of the currencies involved

e) Screen shot of CURRENCY involved

f) CUSTOMER record of the FX Counterparty

g) ACCOUNT record involved in the FX deal

7) FX NETTING

a) NETTING.PARAMETER

b) NP.CONCAT

48 PACS
Support Handbook

c) NETTING.ENTRY

d) NETTING

49 PACS
Support Handbook

FORWARD RATE AGREEMENTS (FRA)


Provide records from the following files:

 FRA.DEAL
 FRA.POSITION (for Trade type of deal) FRA.HEDGE.POSITION (for Hedge type of deal)
 FRA.PARAMETER

1) If the problem is related to LIMIT related error: a) LIMIT.TXNS of the respective contract

2) Accounting / Mismatch related error:

a) Then TRANS.JOURNAL (TRANS.JOURNAL2 –Prior to R8 / TXN.JOURNAL.PRINT – From R8) of the respective date.
b) All the accounting entries.

3) Revaluation related problem:

a) Outcome of the FRA.REVAL report from the HOLD.CONTROL

b) TRANS.JOURNAL (TRANS.JOURNAL2 –Prior to R8 / TXN.JOURNAL.PRINT – From R8) of the respective date.

c) All the accounting entries

4) Delivery related issues:

a) DE.MESSAGE, DE.MAPPING, DE.FORMAT.SWIFT of the related message.

b) output of the DE.O.HANDOFF record using ENQ DE.HANDOFF.DETS OR

c) In Database level run SEE.HANDOFF; enter Delivery key as for the DE.O.HEADER, e.g. SEE.HANDOFF
D2005020400005082700

d) The HOLIDAY records for the Business centers, local currency, Customer’s Residence and the currencies traded

e) CURRENCY records

50 PACS
Support Handbook

Front End
Application works in telnet mode, but not in socket mode:
 Jconman version
 T24 Desktop version
 Communication log in both the cases – telnet and socket mode
 SSL enabled or disabled? – has to be answered
 Multi language set up involved or not? – has to be answered

Browser - TAFC Compliance


Information Required for All Issues
 Whether JCA (AGENT or JMS) architecture is being used or TCServer is used?

(1) T24 release

(2) T24 Browser release (To check (i) Login to T24 Browser (ii) Click "Help" link (iii) Click "About Browser" ).

(3) TCServer/TOCF release

(4) Web Server/App server(Tomcat/Jboss/WebSphere/Weblogic..etc), JSDK and Internet Explorer

 Does the problem occur in Classic / Desktop?


 Is the problem re- creatable via OFS?
 Whether the problem occurs on any particular Browser release.
 Steps for replicating the problem along with screenshots
 Log files from Browser. Kindly refer the below section “Setting Log level to DEBUG for Browser related issues” for getting
these logs.

Setting Log level to DEBUG for Browser related issues


(A) If TCServer is used follow the below steps to give us the TC logs

1. For TCServer log level need to be set as DEBUG as given below

i) Set the log level to DEBUG in the tcslog.properties (which is in …\tcserver\conf\TCServer) file as shown below

log4j.logger.common=DEBUG, file

log4j.logger.tcs=DEBUG, file

log4j.logger.ofs=DEBUG, file

log4j.logger.tcp=DEBUG, file

ii) Set the log level to DEBUG in the tcclient.properties (which is in ... \BrowserWeb\WEB-INF\conf) file as shown below

log4j.logger.common=DEBUG, file

log4j.logger.channels=DEBUG, file

log4j.logger.tcc=DEBUG, file

2. After setting the log level given in step 1, replicate the problem and then send us

i) All the global.log files from the \tcserver\log directory of the TCServer installation

ii) All the global.log files from the \BrowserWeb\WEB-INF\log directory of the Browser installation.

(B) If JCA (AGENT or JMS) architecture is used follow the below steps to give us the agent logs

Please start the jbase agent as shown below

(For ex )

51 PACS
Support Handbook

Jsh-->sh

$jbase_agent -p 20002 -L1 >jagent.out

This will create the jagent.out file bnk.run path . Please send us that file (jagent.out )for our analysis.

Note: The above command works in T24 release prior to R12, From R12 jbase agent log file has to be configured in tafc.ini under
<TAFC_HOME> TAFC\config\default

(C) Procedure to enable BrowserServlet logs

(a) If webserver used is (Tomcat or Jboss 4.2.3 or Websphere or Weblogic ).


1. For enabling BrowserServlet logs, the log level need to be set to DEBUG in the log4j.properties found in "\BrowserWeb\WEB-
INF\classes\" directory as given below

# file appender, location of the file is application server dependant

################################################################################

log4j.appender.logFile=org.apache.log4j.RollingFileAppender

log4j.appender.logFile.layout=org.apache.log4j.PatternLayout

log4j.appender.logFile.layout.ConversionPattern=%n%d [%t] %-5p %c %x - %m%n

log4j.appender.logFile.File= \jboss423\server\default\deploy\BrowserWeb.war\WEB-
INF\log\browser.log

Note: In the above File attribute of the logFile appender, give the complete path where the browser.log has to be written.

log4j.appender.logFile.MaxFileSize=512KB

log4j.appender.logFile.MaxBackupIndex=999

# default logging in Browser

################################################################################

# default logging is to the console, for output to the file, comment following line and uncomment the subsequent line

#log4j.logger.com.temenos=ERROR, console

log4j.logger.com.temenos=DEBUG, logFile

# default logging for beans and other classes in the t24browser package and its subpackages

################################################################################

log4j.logger.com.temenos.t24browser=DEBUG

# default logging for servlets and servlet filters

################################################################################

log4j.logger.com.temenos.t24browser.servlets=DEBUG

2. After setting the BrowserServlet log level as given in step 1, replicate the problem and then send us all the log files from the File
attribute of the logFile appender (for e.g in this case the browser.log files from it is the
\jboss423\server\default\deploy\BrowserWeb.war\WEB-INF\log directory)

Note: While using IBM Web sphere, Remove the log4j.jar file from the BrowserWeb.war/WEB-INF/lib and place it under the IBM
Websphere’s lib directory.

Browser - TAFJ Compliance


Information Required for All Issues
Information needed

(1) T24 release

(2) T24 Browser release (To check (i) Login to T24 Browser (ii) Click "Help" link (iii) Click "About Browser" ).

52 PACS
Support Handbook

(3) TOCF release

(4) Web Server/App server(Tomcat/Jboss/WebSphere/Weblogic..etc), JSDK and Internet Explorer

(5) TAFJ version and DB details being connected.

 Does the problem occur in Classic ?


 Is the problem re- creatable via OFS?
 Whether the problem occurs on any particular Browser release.
 Steps for replicating the problem along with screenshots
 Log files from Browser. Kindly refer the below section “Setting Log level to DEBUG for Browser related issues” for getting
these logs.

Setting Log level to DEBUG for Browser related issues


(A) IF TAFJ architecture has been used requires the below steps to be get the TAFJ logs

a. Set the log level to DEBUG in the TAFJTrace.properties present under the 'conf' directory of TAFJ home directory.

Change INFO to DEBUG in the following lines in TAFJTrace.properties

log4j.logger.T24=DEBUG, t24

log4j.logger.DATABASE=DEBUG, database

log4j.logger.RUNTIME=DEBUG, runtime

log4j.logger.MDB=DEBUG, mdb

log4j.logger.EJB=DEBUG, ejb

after making the above changes in TAFJTrace.properties, kindly clear all the log files in 'log' and 'log_T24' directory and restart the
Web Application Server (i.e. jBoss, Websphere, Weblogic).

b. Recreate the problem and send us the following files in sync for analysis.

a) Once the problem replicates, send us all the T24.log files from …\<TAFJ_HOME>\log_T24 directory.

b) All the database.log, runtime.log, mdb.log, ejb.log files from …\<TAFJ_HOME>\log directory.

(B) Procedure to enable BrowserServlet logs

(a) If webserver used is (Jboss 4.2.3 or Websphere or Weblogic ).

1. For enabling BrowserServlet logs, the log level need to be set to DEBUG in the log4j.properties found in "\BrowserWeb\WEB-
INF\classes\" directory as given below

# file appender, location of the file is application server dependant

################################################################################

log4j.appender.logFile=org.apache.log4j.RollingFileAppender

log4j.appender.logFile.layout=org.apache.log4j.PatternLayout

log4j.appender.logFile.layout.ConversionPattern=%n%d [%t] %-5p %c %x - %m%n

log4j.appender.logFile.File= \jboss423\server\default\deploy\BrowserWeb.war\WEB-INF\log\browser.log

Note: In the above File attribute of the logFile appender, give the complete path where the browser.log has to be written.

log4j.appender.logFile.MaxFileSize=512KB

log4j.appender.logFile.MaxBackupIndex=999

# default logging in Browser

################################################################################

# default logging is to the console, for output to the file, comment following line and uncomment the subsequent line

#log4j.logger.com.temenos=ERROR, console

53 PACS
Support Handbook

log4j.logger.com.temenos=DEBUG, logFile

# default logging for beans and other classes in the t24browser package and its subpackages

################################################################################

log4j.logger.com.temenos.t24browser=DEBUG

# default logging for servlets and servlet filters

################################################################################

log4j.logger.com.temenos.t24browser.servlets=DEBUG

2. After setting the BrowserServlet log level as given in step 1, replicate the problem and then send us all the log files from the File
attribute of the logFile appender (for e.g in this case the browser.log files from it is the
\jboss423\server\default\deploy\BrowserWeb.war\WEB-INF\log directory)

Note: While using IBm Web sphere, Remove the log4j.jar file from the BrowserWeb.war/WEB-INF/lib and place it under the IBM
Websphere’s lib directory.

54 PACS
Support Handbook

Browser connection issues - TAFC Compliance


Generic information needed irrespective of TCServer/JCA used
 Output of jdiag –dvL (output will be stored in jdiag.out. Please attach the jdiag.out file).
 channels.xml & browserConnection.xml files from \BrowserWeb\Web-inf\conf directory
 browserParameters.xml from \BrowserWeb\ directory
 OFS.SOURCE record used for Browser connection

With TCServer
 tcserver.xml & environment.vars files from the \tcserver\conf directory

With JCA

The JCA connection factory properties


 For JBOSS this is available in the t24-ds.xml file found in the /JBOSS/server/default/deploy directory

In R09 Release ( jremote and tocfee.ear used)

 For WebSphere this is available in the Admin console from the path "Resource adapters > jRemote > J2C connection factories
> T24 JCA Connection Factory > Custom properties".
 For Weblogic this is available in the Admin console from the path "Deployments > jremote-ra > Configuration > Outbound
Connection Pools > JConnectionFactory > Properties".

In R10 and higher Releases ( tocft24-ra.rar and tocfee.ear used)

 For WebSphere this is available in the Admin console from the path "Resource adapters > TOCF T24 Resource Adapters >
J2C connection factories > T24 JCA Connection Factory > Custom properties".
 For Weblogic this is available in the Admin console from the path "Deployments > tocfT24ra-ra > Configuration > Outbound
Connection Pools > JConnectionFactory > Properties".

JMS messaging configuration


 For JBOSS this is available in the t24-destinations-service.xml file found in the /JBOSS/server/default/deploy directory
 For WebSphere this is available in the Admin console from the path "Resources >JMS" inside the sub path’s, Connection
Factories, Queues & Queue connection factory
 For Weblogic this is available in the Admin console from the path "Services > Messaging > JMS Modules > JMSModuleT24"

All the Application Server(JBOSS/WebSphere/WebLogic) logs


 For JBOSS this is available in the /JBOSS/server/default/log directory
 For WebSphere this is available in the /WebSphere/profiles/AppSrv01/logs/server1 directory
 For Weblogic this is available in the /WebLogic/user/projects/domains/base_domain/servers/AdminServer/logs directory

Browser connection issues - TAFJ Compliance


Generic information needed
 browserParameters.xml from \BrowserWeb\ directory
 OFS.SOURCE record used for Browser connection

TAFJ ARCHITECTURE
All the Application Server(JBOSS/WebSphere/WebLogic) logs

 For JBOSS this is available in the /JBOSS/server/default/log directory


 For WebSphere this is available in the /WebSphere/profiles/AppSrv01/logs/server1 directory

55 PACS
Support Handbook

 For Weblogic this is available in the /WebLogic/user/projects/domains/base_domain/servers/AdminServer/logs directory

Time Out
• Tafj session timeout is defined in ejb-jar.xml file under TAFJJEE_EAR.ear\TAFJJEE_EJB.jar\META-INF\ path. This is defined as
below in seconds,

<env-entry>

<env-entry-name>com.temenos.tafj.sb.OFSProcessingBean/ofsTimeout</env-entry-name>

<env-entry-type>java.lang.Integer</env-entry-type>

<env-entry-value>60</env-entry-value>

</env-entry>

56 PACS
Support Handbook

DESKTOP
General Queries for All Issues
 Does the problem occur only in T24 Desktop or Classic?
 Does the problem occur on any particular T24 Desktop Release?
 Does it occur after installation of any T24 Update?
 Steps for replicating the problem along with screenshots.
 Communication log
 Does the problem occur in a particular machine or all machines?

Desktop hanging
 Press the “Details” button and send us the contents shown in the window.
 Does the problem continue to occur on pressing “Resume Wait” option
 If the problem happens while running any local application or enquiry. Send us the local routines involved
 If enquiry listing takes time, do a “time SELECT “output from jBASE prompt for the same file.
 Jsh->time SELECT <file name>
 Screen shot of Communication tab from T24 Desktop options.

Printing issues in Browser


 Screenshots of the error messages;
 DEAL.SLIP.FORMAT/ENQUIRY.REPORT record
 Whether the Print problem is with Server print or Local Print
 Whether the Print problem occurs only on enquiries or versions or any specific application
 If the problem is specific to some users then send the BROWSER.PREFERENCES record of the USER
 jBASE .profile
 environment.vars from the \TCServer\conf\TCServer directory

T24 Web Services - TAFC Compliance


The following would be the mandatory details for all TWS issues.

These are the basic information required.

1)The TWS flavour used, i.e TWS(EE) or TWS(.NET)

If TWS(EE)
1. a)The version of TWS(EE) used

2. a)LIST F.SPF from jshell prompt

3. a)The log files for the project and detailed jbase_agent log (starting jbase_agent in –L mode)

4. a)The war file created

5. a)The enquiry/Version record used if problem faced in web service creation. Corresponding PW.ACTIVITY and EB.SERVICE record
from T24

6. a)In case jboss is used, The t24-ds.xml file from the <jboss installation directory>\server\default\deploy> folder

7.a) In case jboss is used, the jboss log file from the <jboss installation directory>\server\default\log> folder

If TWS(.NET)
1. b)The version of TWS(.NET) used

57 PACS
Support Handbook

2. b)LIST F.SPF from jshell prompt

3. b)The log files from both project log and T24Service Connector log Folder

4. b) Detailed jbase_agent log (starting jbase_agent in –L mode)

5. b)connectors.xml file from conf directory of Service Connector

6.b)The enquiry/Version record used if problem faced in web service creation. Corresponding PW.ACTIVITY and EB.SERVICE record
from T24

T24 Web Services - TAFJ Compliance


The following would be the mandatory details for all TWS issues.

These are the basic information required.

1)The TWS flavour used, i.e TWS(EE) or TWS(.NET)

If TWS(EE)
1. a)The version of TWS(EE) used

2. a)LIST F.SPF from jshell prompt

3. a)The log files for the project and detailed jbase_agent log (starting jbase_agent in –L mode)

4. a)The war file created

5. a)The enquiry/Version record used if problem faced in web service creation. Corresponding PW.ACTIVITY and EB.SERVICE record
from T24

6. a)In case jboss is used, The t24-ds.xml file from the <jboss installation directory>\server\default\deploy> folder

7.a) In case jboss is used, the jboss log file from the <jboss installation directory>\server\default\log> folder

If TWS(.NET)
1. b)The version of TWS(.NET) used

2. b)LIST F.SPF from jshell prompt

3. b)The log files from both project log and T24Service Connector log Folder

4. b) Detailed jbase_agent log (starting jbase_agent in –L mode)

5. b)connectors.xml file from conf directory of Service Connector

6.b)The enquiry/Version record used if problem faced in web service creation. Corresponding PW.ACTIVITY and EB.SERVICE record
from T24

FUNDS.TRANSFER - TAFC Compliance


For all problems,Provide screen dumps of the following records:
 FUNDS.TRANSFER
 STMT.ENTRY records
 CATEG.ENTRY records
 FT.TXN.TYPE.CONDITION record
 FULL VIEW OF THE ACCT.ACTIVITY for the DEBIT ACCOUNT AND CREDIT ACCOUNT records
 FULL VIEW OF ACCOUNT records
 VERSION and VERSION CONTROL and routines attached

Following listings

>TERM 800

58 PACS
Support Handbook

>LIST FXXX.STMT.ENTRY WITH TRANS.REFERENCE LIKE “...’’...” BY BOOKING.DATE BOOKING.DATE VALUE.DATE


AMOUNT.LCY AMOUNT.FCY TRANSACTION.CODE ACCOUNT.NUMBER COMPANY.CODE SYSTEM.ID

>LIST FXXX.STMT.ENTRY.DETAIL WITH TRANS.REFERENCE LIKE “...’’...” BY BOOKING.DATE BOOKING.DATE VALUE.DATE


AMOUNT.LCY AMOUNT.FCY TRANSACTION.CODE ACCOUNT.NUMBER COMPANY.CODE SYSTEM.ID

>LIST FXXX.CATEG.ENTRY WITH TRANS.REFERENCE LIKE “...’’...” BY BOOKING.DATE BOOKING.DATE VALUE.DATE


AMOUNT.LCY AMOUNT.FCY TRANSACTION.CODE PL.CATEGORY COMPANY.CODE SYSTEM.ID

>LIST FXXX.CATEG.ENTRY.DETAIL WITH TRANS.REFERENCE LIKE “...’’...” BY BOOKING.DATE BOOKING.DATE


VALUE.DATE AMOUNT.LCY AMOUNT.FCY TRANSACTION.CODE PL.CATEGORY COMPANY.CODE SYSTEM.ID

In case if it is a BC type transaction, prints of the following records

 FT.LOCAL.CLEARING record
 FT.BC.PARAMETER record

Discrepancy in charges calculations,


Provide screen dumps of the following records

 FUNDS.TRANSFER record
 FT.CHARGE.TYPE record
 FT.COMMISSION.TYPE record
 FT.APPL.DEFAULT record
 FT.GROUP.CONDITION record
 CUSTOMER.CHARGE record

Discrepancy in rate calculations:


Provide screen dumps of the following records

 FUNDS.TRANSFER record
 FT.GROUP.CONDITION record
 CURRENCY record.
 FT.APPL.DEFAULT record
 COMPANY record

Problem with ID formation:


AUTO.ID.START

F.LOCKING

T24.PAYMENTS.INFO
The tool T24.PAYMENTS.INFO can be used to extract FT related files:

The tool and the user guide is available in the link https://tcsp.temenos.com/Pages/ToolsnUtil.aspx

Files extracted using the tool:

FUNDS.TRANSFER record

DEBIT AND CREDIT ACCOUNT

DEBIT AND CREDIT CURRENCY

DEBIT/CREDIT/TRANSACTION COMPANY

FT.TXN.TYPE.CONDITION

FT.CHARGE.TYPE

FT.COMMISSION.TYPE

59 PACS
Support Handbook

FT.GEN.CONDITION

FT.GROUP.CONDITION

CUSTOMER.CHARGE

F.FT.APPL.DEFAULT

FT.LOCAL.CLEARING

F.FT.BC.PARAMETER

DELIVERY.IN.REF/DELIVERY.OUT.REF

ENQ TXN.ENTRY

ENTRIES

ENTRY.HOLD

LOCAL CLEARING:
If FT.TAPES is used for local clearing then

 The FT.TAPE.PARAMS record


 AC.ENTRY.PARAM record and source code of local routines attached.
 Sample strings passed
 AC.INWARD.ENTRY records
 STMT.ENTRY records
 CATEG.ENTRY records

In case OFS.CLEARING.MANAGER is used

 AC.ENTRY.PARAM record and source code of local routines attached.


 Sample strings used
 AC.INWARD.ENTRY records
 STMT.ENTRY records
 CATEG.ENTRY records

BULK.PROCESSING:
 Upload file used
 EB.FILE.UPLOAD
 FT.BULK.UPDATE.TYPE
 EB.FILE.UPLOAD.TYPE
 FT.BULK.MASTER
 FT.BULK.ITEM
 OFS.REQUEST.DETAIL for corresponding processing

60 PACS
Support Handbook

Guarantees

Miscellaneous Deals

For all MD problems


 MD.DEAL
 MD.BALANCES

If Problem is related to Participation, Commission, Provision:


 MD.PART.CSN.BALANCES
 MD.PROV.BALANCES
 MD.CSN.RATE.CHANGE

If problem is related to future dated events, Maturity:


 MD.EOD.LIST
 MD.SCHEDULES
 MD.SCHED.DATES

Balance mismatch in MD
For balance mismatch, supply us with details of STMT.ENTRY, CATEG.ENTRY and RE.CONSOL.SPEC.ENTRY.

Problem with a particular contract: (following details are needed)

MD.PARAMETER

MD.DEAL

MD.BALANCES

EB.CONTRACT.BALANCES

61 PACS
Support Handbook

LOANS AND DEPOSITS


Problem is Commitment contract
 The main Commitment contract and its history records
 All the drawdown contracts and its history records
 The entire draw down records can be taken from the LD.COMMITMENT
 The LD.TRANCHE.DETAILS and LMM.ACCOUNT.BALANCES record

Problem in maturity of LD contract


After the maturity date of the LD contract, it will be moved to History after the number of days set in LMM.INSTALL.CONDS. To
analyse this kind of problems we need the following.

 LD.LOANS.AND.DEPOSITS
 LMM.ACCOUNT.BALANCES
 LMM.INSTALL.CONDS
 RE.LD.ACC.BAL / EB.CONTRACT.BALANCES
 RE.CONSOL.LOAN / RE.CONSOL.CONTRACT
 jshow –c LD.MATURE.COMMT

Problem related to LD Delivery Advices Generation


 LD.LOANS.AND.DEPOSITS
 LD.SCHEDULE.DEFINE
 LMM.ADVICES
 LMM.ACTIVITY
 BASIC.RATE.TEXT(in case of Floating LD contract advices)
 LMM.INSTALL.CONDS
 DE.MAPPING and DE.MESSAGE record for the corresponding SWIFT/ PRINT message
 LD.PAYMENT.ENTRY for Payment related messages
 CURRENCY record for Payment related advices.
 DE.FORMAT.SWIFT / DE.FORMAT.PRINT record
 DE.O.HEADER record
 Output of the enquiry DE.HANDOFF.DETS for the delivery key
 Output of the enquiry DE.MSG.SUM for the delivery key

End of Day failures


 The specific job name and BATCH record name.
 A screen print of the error message.

Screen shots of the following.

 LD.LOANS.AND.DEPOSITS
 LMM.ACCOUNT.BALANCES
 LMM.SCHEDULES.PAST
 LMM.SCHEDULE.DATES
 LMM.SCHEDULES
 The system run date.
 Whether the system is a single or multi-company set-up.

62 PACS
Support Handbook

 A full print of the COMO for the failed process.

At the time of COB hang /loop /locks , along with the above information :

 Mw42 -f
 Where (v
 jshow of the problematic job that crashes.

Balance Mismatch in LD
For balance mismatch, supply us with details of STMT.ENTRY, CATEG.ENTRY and RE.CONSOL.SPEC.ENTRY. (Refer to listing
mentioned in section 2.1 Balance Mismatch Messages of Chapter 2, Accounting and Reporting.), along with the extraction of
RE.STAT.MISMATCH and RE.STAT.BAL.REC report on the same day, where listings are taken.

MANAGEMENT INFORMATION SYSTEM (MIS)


Discrepancy in the balance value of the BALANCE.MOVEMENT records:
 MI.DATES record.
 MI.PARAMETER
 BALANCE.MOVEMENT record.
 REBUILD.BAL.MVMT record if BALANCE.MOVEMENT built online/service
 If problem pertains to Account records of Balance Movement, provide prints of ACCT.ACTIVITY records.
 If problem pertains to Contracts of Balance Movement, provide prints of CONT.ACTIVITY records.
 If problem pertains to Missing CONT.ACTIVITY/CONT.CONT.ACTIVITY or Contracts of Balance Movement, provide the
below listings.

a) >TERM 300

b) >LIST FXXX.RE.CONSOL.SPEC.ENTRY WITH TRANS.REFERENCE LIKE ...<<contract id>>... BY BOOKING.DATE


TRANS.REFERENCE BOOKING.DATE VALUE.DATE TRANSACTION.CODE AMOUNT.LCY AMOUNT.FCY CURRENCY
EXCHANGE.RATE PRODUCT.CATEGORY CONSOL.KEY.TYPE SYSTEM.ID

c) >LIST FXXX.RE.SPEC.ENTRY.DETAIL WITH TRANS.REFERENCE LIKE ...<<contract id>>... BY BOOKING.DATE


TRANS.REFERENCE BOOKING.DATE VALUE.DATE TRANSACTION.CODE AMOUNT.LCY AMOUNT.FCY CURRENCY
EXCHANGE.RATE PRODUCT.CATEGORY CONSOL.KEY.TYPE SYSTEM.ID

 Prints of related Contract/Account records.

If the problem is for online rebuilding BM record

 Full view of REBUILD.BAL.MVMT

Online rebuilding of MI database

 Full view of MI.BUILD.DATABASE


 The related MI.DB.DEFINITION record
 MI.SELECTION and MI.COLUMN record attached in MI.DB.DEFINITION
 MI.PARAMETER

Money Market
Provide records from the following files:
 MM.MONEY.MARKET
 LMM.ACCOUNT.BALANCES
 LMM.SCHEDULES.PAST
 LMM.SCHEDULE.DATES
 LMM.SCHEDULES

63 PACS
Support Handbook

For records moved to history:


 LMM.ACCOUNT.BALANCES.HIS
 LMM.SCHEDULE.PAST.HIS

If the problem is related to

1) Online FATAL.ERROR on LIMIT related (either while input, amend, reversal), then LIMIT.TXNS of the respective contract

2) Accounting error, then TRANS.JOURNAL (TRANS.JOURNAL2 –Prior to R8 / TXN.JOURNAL.PRINT – From R8) of the
respective date, EB.SYSTEM.SUMMARY and EB.JOURNAL.SUMMARY along with latest mismatch report.

3) Balance Mismatch, then all the accounting entries. (Format and the necessary table details are specified in BALANCE MISMATCH
section), Full view of CAL record, Full view of ECB and LMM.ACCOUNT.BALANCES (if problematic MM deal is identified),
EB.SYSTEM.SUMMARY and EB.JOURNAL.SUMMARY along with latest mismatch report.

4) If MM deals NOT moved to history, then

a) Full view of LMM.INSTALL.CONDS

5) If COB crashes

a) Respective COMO

b) Full view of all history records for the MM deal shown in crash

c) Full view of LMM.SCHEDULE.DATES for the MM deal shown in crash

d) Full view of LMM.SCHEDULES for the MM deal shown in crash

e) Full view of LMM.ACCOUNT.BALANCES for the MM deal shown in crash

f) Full view of EB.CONTRACT.BALANCES for the MM deal shown in crash

6) If COB hangs, then

a) SHOW-ITEM-LOCKS

b) WHERE (V

c) mw42

d) Full view of LMM.SCHEDULE.DATES for the first MM deal in the joblist

e) Full view of all history records for the first MM deal in the joblist

7) Online validation errors, then

a) Whether the problem occurs in browser and/or classic

b) Screen shots of exact steps followed( Sequence of input)

c) Full view of SPF record

8) Delivery related issues:

a) DE.MESSAGE, DE.MAPPING, DE.FORMAT.SWIFT of the related message

b) Outcome of the DE.O.HANDOFF record using ENQ DE.HANDOFF.DETS OR

c) In Database level run SEE.HANDOFF; enter Delivery key as for the DE.O.HEADER, e.g. SEE.HANDOFF
D200502040000508270

d) Full view of LMM.ADVICES for contract category

e) Full view of LMM.INSTALL.CONDS.

9) If the problem is related to Online maturity:

i. TSA.SERVICE record of MM.ONLINE.MAT

ii. All history records of MM deal from front end.

iii. COMO of BATCH MM.ONLINE.MAT

64 PACS
Support Handbook

Mortgages
Balance mismatch in MG
For balance mismatch, supply us with details of STMT.ENTRY, CATEG.ENTRY and RE.CONSOL.SPEC.ENTRY.

Problem is with any particular contract


 MG.PARAMETER
 MG.MORTGAGE
 MG.BALANCES
 RE.MG.BALANCES
 MG.PAYMENT
 EB.CONTRACT.BALANCES

Problem of MG.BALANCES becomes null


 MG.PARAMETER
 MG.MORTGAGE
 MG.BALANCES
 EB.CONTRACT.BALANCES
 ENQ STMT.ENT.BOOK for the MORTGAGE account.
 STMT.ENTRY,CATEG.ENTRY,RE.CONSOL.SPEC.ENTRY of the Contract

Unprocessed schedules
 MG.MORTGAGE
 MG.BALANCES
 EB.CONTRACT.BALANCES
 ENQ STMT.ENT.BOOK for the MORTGAGE account.

Error message occurred during online:


 MG Contract
 Screenshot of the error message
 MG.BALANCES

Problem at Rate changes


 MG.MORTGAGE
 MG.BALANCES
 MG.RATE.CONTROL
 MG.RATE.CONTROL.HIST

Problem in maturity of MG contract


After the maturity date of the MG contract, it would not be moved to History after the number of days set in MG.PARAMETER. To
analyse this kind of problems we need the following.

 MG.PARAMETER
 MG.MORTGAGE
 MG.BALANCES
 EB.CONTRACT.BALANCES

65 PACS
Support Handbook

Mutual Funds
The following basic details need to be provided for all issues based on the problem faced.

 MF.PARAMETER

Related to Retail side (Participation account and agent) and charges


 CUSTOMER (Retail)
 CUSTOMER.SECURITY (Retail)
 ACCOUNT
 SEC.ACC.MASTER (Retail)
 CONDITION.PRIORITY
 CUSTOMER.CHARGE
 SCTR.CHARGE.PARAMETER
 SCTR.GEN.CONDITION
 SCTR.GROUP.CONDITION
 SECURITY.MASTER, SUB.ASSET.TYPE, ASSET.TYPE
 FT.COMMISSION.TYPE
 MF.AMORT.MASTER (to amortise the initial expenses incurred by a fund)

Related to fund management


 CUSTOMER (for fund management)
 CUSTOMER.SECURITY (for fund management)
 SEC.ACC.MASTER (for fund management)
 ACCOUNT
 SECURITY.MASTER
 MF.FUND.MASTER
 MF.ROUNDING.PARAM

Related to order processing flow


 MF.ORDER.BY.CUST
 MF.ORDER
 MF.EXECUTE.ORDERS (If involved)
 MF.TRADE
 COMO and TSA.SERVICE of MF.PROCESSING

Related to general processing and files getting updated


 Transactions involved like MF.TRADE, POSITION.TRANSFER, DIARY (also underlying DIARY.TYPE), ENTITLEMENT,
SC.BLOCK.SEC.POS
 SECURITY.POSITION
 SECURITY.TRANS
 TRN.CON.DATE, TRN.CON.TRADE.DATE
 MF.TXN.LINK
 Output of Core enquiries like SC.HOLD.SUM, SC.VAL.COST, SC.VAL.MARKET, SC.POS.DET, CATEG.ENT.BOOK,
MF.PENDING.ORDERS, MF.TRADES.TODAY, MF.PRE.ORDERS, MF.PLANS.OUTSTANDING, NAV.MVMT.HISTORY.

66 PACS
Support Handbook

NON-DELIVERABLE DEAL (ND)


Provide records from the following files by default:
 ND.DEAL
 ND.PARAMETER
 ND.BALANCES
 ND.TYPE

Nostro Reconciliation
Problem related to Ledger & Statement MT950/940 Messages,
 ACCOUNT.STATEMENT
 F.DE.O.MSG.RECS
 NR.PARAMETER
 EB.PHANTOM>NR.DECODE
 NR.STATEMENT for the problematic account
 NR.ITEMS for the problematic account
 NR.AUTOMATCH record verified
 DE.O.HEADER
 ENQ DE.MSG.SUM for the above Delivery
 Activation file: F.RECS.OUT.LIST
 F.NR.DIVERT
 SWIFT (950) messages received
 AGENCY record

From R12 release:


 Concat file NR.STMT.INDEX
 Como for the service NR.PROCESS.MESSAGES
 BATCH>XXX/NR.AUTOMATCH
 Como for the service NR.AUTOMATCH
 Files need to be requested from the jshell prompt:
 Jsh->LIST.ITEM FXXX.NR.STATEMENTS WITH @ID LIKE …
 Jsh->LIST.ITEM FXXX.NR.ITEMS WITH @ID LIKE …
 Jsh->LIST.ITEM F.RECS.OUT.LIST WITH @ID LIKE …
 jsh ->LIST F.DE.SWIFT.ADDRESS WITH @ID LIKE ...
 Note: Replace BIC with valid Sender and Receiver address.

For the ENQUIRY related issues:


 NR.ITEMS.LEDGER
 NR.ITEMS.STATEMENT
 NR.MATCHED.ITEMS
 NR.STMT.TOTALS
 NR.TOT.SUMMARY

67 PACS
Support Handbook

PAYMENT DUES
Balance mismatch in PD
For balance mismatch, supply us with details of STMT.ENTRY, CATEG.ENTRY and RE.CONSOL.SPEC.ENTRY. (Refer to listing
mentioned in section 2.1 Balance Mismatch Messages of Chapter 2, Accounting and Reporting.) along with the extraction of
RE.STAT.MISMATCH and RE.STAT.BAL.REC report on the same day, where listings are taken.

Problem is with any particular contract


 PD.PARAMETER record of that contractPD contract details in full view
 PD.BALANCES record.
 RE.CONTRACT.BALANCES / EB.CONTRACT.BALANCES for that contract
 PD.REPAYMENT for repayment type of problem.
 PD.RATES for PE/PS rates problem
 PD.REPAYMENT for repayment related problem
 PD.ONLINE.PAYMENT for PD payment related problem using FT/DC

Problem of PD.BALANCES moving to history without repayment or wrong values in


PD.BALANCES
 PD.PARAMETER
 PD record
 PD.BALANCES
 ENQ STMT.ENT.BOOK for the repayment account.
 RE.CONSOL.SPEC.ENTRY for the problematic contract.

Account overdrawn by PD
 PD contract
 ENQ STMT.ENT.BOOK
 PD.PARAMETER
 ACCOUNT record.
 ACCOUNT.PARAMETER record.
 LIMIT record of Corresponding PD

Error message occurred during online


 PD Contract
 Screenshot of the error message.

Problem with Provisioning in PD


 ASSET.CLASS.PARAMETER
 LN.ASSET.CLASS
 PD.PARAMETER
 PD.PAYMENT.DUE record and its PD.BALANCES record
 LN.TXN.CODES
 Underlying LD contract and its LMM.ACCOUNT.BALANCES
 LN.PROV.BALANCES and LN.PROV.BALANCES.DETAILS

68 PACS
Support Handbook

Payments
DATA.CAPTURE
GL difference due to Data Capture and problematic Data Capture ID is NOT known:
 TRANS.JOURNAL (TRANS.JOURNAL2 –Prior to R8 / TXN.JOURNAL.PRINT – From R8)of DC module.
 ACCOUNT.PARAMETER record.
 Screenshot of the reports DATA.CAP.ACTIVITY.JNL, DATA.CAP.DIFF.ENTRIES and DATA.CAP.SUSP.ENTRIES
 EB.SYSTEM.SUMMARY records for the GL difference found date and previous date.

GL difference due to Data Capture and problematic Data Capture ID IS known:


 Full view of DC.PARAMETER
 Full view of EB.JOURNAL.SUMMARY
 TRANS.JOURNAL/TXN.JOURNAL.PRINT report for the day GL difference raised.
 From jshell:

>LIST-ITEM FXXX.DC.BATCH.CONTROL LIKE <DC.ID>...

>LIST FXXX.DC.BATCH.CONTROL.HIST LIKE <DC.ID>...

>LIST FXXX.DATA.CAPTURE WITH @ID LIKE <DC.ID>...

>LIST FXXX.DATA.CAPTURE$NAU WITH @ID LIKE <DC.ID>...

>LIST FXXX.DATA.CAPTURE$HIS WITH @ID LIKE <DC.ID>...

Not able to input, delete or authorise


 Whether the first Id of the DC item input is done manually or pressing F3.
 Steps followed to input the problematic DC.
 Full view of the corresponding DC.BATCH.CONTROL record.
 If any of the version record is used to input the DC item, then Full view of VERSION record with the source of the routines.
(if attached any)
 Full view of ACCOUNT.PARAMETER record.
 Kindly confirm whether the problem happened in Browser, classic or desktop?

DIRECT DEBITS
For all problems
Screen Dumps from the following files:

 DD.PARAMETER
 DD.ITEM
 DD.PROCESS.LIST
 DD.DDI
 DD.ACTIVITY
 DD.GENERATE.FILES.SEQ
 DD.STANDALONE.FQU.LIST
 TRANS.FWD
 STMT.ENTRY records
 If the DD is attached to a mortgage, then MORTGAGE record

69 PACS
Support Handbook

 DD.OUT.FORMAT
 DD.IN.FORMAT
 DD.HEADER

POSITION.MANAGEMENT
Problem in Position Management enquiries.
Provide screen dumps of the following records

 Enquiry results.
 Screenshots of contracts involved.
 Corresponding PM.DLY.POSN.CLASS record
 Corresponding PM.TRAN.ACTIVITY record. PM.POSN.CLASS record.
 PM.ENQ.PARAM Record
 Full view of PM.POSN.REFERENCE record with @ID specified in the field POSN.REF of PM.ENQ.PARAM record
 Full view of PM.CALENDAR record with @ID specified in the field CALENDAR of PM.ENQ.PARAM record
 Full view of the Enquiry Record with @ID PM.FXPOS
 Full view of the Enquiry Record with @ID DPC.TXNS
 Full view of PM.PARAMETER record with @ID SYSTEM
 Full view of BATCH record with @ID XXX/PM.EOD2
 PM.AC.PARAM with record @ID as CAS
 PM.LD.PARAM with record @ID as
 PM.SC.PARAM if the problem is due to securities related transactions/lines

Process Workflow
Some of the general information needed for initial analysis
 PW.ACTIVITY
 PW.PROCESS.DEFINITION
 PW.ACTIVITY.TXN
 PW.PROCESS

Here are some of scenarios/problems for which the information required to analyze are as follows

For problems related to M APPING


 EB.MAPPING.SOURCE
 EB.FORMAT.ENTRY
 PW.MAPPING
 PW.MAP.SOURCE
 TSA.SERVICE of BNK/PW.MAPPING
 PW.ACTIVITY
 PW.PROCESS.DEFINITION
 For problems relating to STATUS of PROCESS FLOW
 PW.TRANSITION
 PW.STATUS
 PW.PROCESS.DEFINITION

70 PACS
Support Handbook

 PW.ACTIVITY

REPO (RP)
Provide records from the following files:
 REPO.TYPE
 REPO
 REPO.PARAMETER
 REPO.POSITION
 SECURITY.POSITION
 SECURITY.MASTER
 PRICE.TYPE specified in SECURITY.MASTER
 RESO.POSITION

1) Online FATAL.ERROR on LIMIT related (either while input, amend, reversal), then LIMIT.TXNS and LIMIT.DAILY.OS of the
respective Repo generated MM contract.

2) Accounting error, then TRANS.JOURNAL (TRANS.JOURNAL2 –Prior to R8 / TXN.JOURNAL.PRINT – From R8)of the respective
date highlighting MM and Security Transfer.

3) Balance Mismatch, then all the accounting entries matching the underlying MM.MONEY.MARKET and SECURITY.TRANSFER.

4) Delivery related, then DE.MESSAGE, DE.MAPPING, DE.FORMAT.SWIFT of the related message

 Outcome of the DE.O.HANDOFF record using ENQ DE.HANDOFF.DETS OR


 In Database level run SEE.HANDOFF; enter Delivery key as for the DE.O.HEADER, e.g. SEE.HANDOFF
D2005020400005082700
 EB.ACTIVITY and EB.ADVICES for RP activities.

5) Online validation errors, then

 Whether the problem occurs in browser and/or classic


 Screen shots of exact steps followed( Sequence of input)

71 PACS
Support Handbook

Reporting
Balance Mismatch
Balance Mismatch Messages – IC Mismatches
1. Full view of below CAL records from the problematic company

2. Full view of ACCOUNT.ACCRUAL record for the problematic company

3. Full view of COMPANY record and SPF record.

4. Extract and send us the output of the below commands,

5. Full view of the problematic report for the problematic company

jsh->TERM 300

jsh->COMO ON SPEC.LIST

jsh->SELECT FXXX.RE.CONSOL.SPEC.ENT.KEY WITH @ID LIKE <<CAL>>...

>QSELECT FXXX.RE.CONSOL.SPEC.ENT.KEY

>LIST FXXX.RE.CONSOL.SPEC.ENTRY BOOKING.DATE VALUE.DATE AMOUNT.LCY AMOUNT.FCY TRANS.REFERENCE


TRANSACTION.CODE CONSOL.KEY.TYPE SYSTEM.ID NOPAGE

>COMO OFF

>TERM 300

>COMO ON SPEC.DETAIL.LIST

>SELECT FXXX.RE.SPEC.ENTRY.XREF LIKE <<CAL>>...

>QSELECT FXXX.RE.SPEC.ENTRY.XREF

>LIST FXXX.RE.SPEC.ENTRY.DETAIL BOOKING.DATE VALUE.DATE AMOUNT.LCY AMOUNT.FCY TRANS.REFERENCE


TRANSACTION.CODE CONSOL.KEY.TYPE SYSTEM.ID NOPAGE

>COMO OFF

>TERM 300

>COMO ON ACCT.LIST

>SELECT FXXX.RE.CONSOL.CONTRACT WITH @ID EQ "<<CAL>>"

>QSELECT FXXX.RE.CONSOL.CONTRACT

>LIST FXXX.ACCOUNT TOTAL ACCR.DR.AMOUNT ACCR.DR.CATEG ACCR.DR.TRANS TOTAL ACCR.CR.AMOUNT


ACCR.CR.CATEG ACCR.CR.TRANS NOPAGE

>COMO OFF

>TERM 300

>COMO ON ECB.LIST

>SELECT FXXX.EB.CONTRACT.BALANCES WITH CONSOL.KEY LIKE <<CAL>>...

>LIST FXXX.EB.CONTRACT.BALANCES TYPE.SYSDATE OPEN.BALANCE CREDIT.MVMT DEBIT.MVMT CURR.ASSET.TYPE


OPEN.ASSET.TYPE PREV.ASSET.TYPE NOPAGE

>COMO OFF

>TERM 300

>LIST FXXX.EB.SYSTEM.SUMMARY AL.CCY.MKT AL.CCY AL.CCY.BAL.AMT AL.LCL.BAL AL.CCY.POSN AL.LCL.POS


AL.CCY.EXCEP AL.LCY.EXCEP AL.TOTAL.LCY PL.TOTAL.LCY EXCEPT.AMT.LCY BY.DSND @ID NOPAGE

CAL CPL keys are not reported in CRF


1. Full view of the detailed CRF report

72 PACS
Support Handbook

2. Full view of the RE.STAT.REP.LINE record (the line where the key is mapped and the line to be mapped)
3. Full view of the RE.STAT.LINE.CONT record (the line where the key is mapped and the line to be mapped)

GL differences
1. Full view of latest EB.SYSTEM.SUMMARY record
2. Latest RE.STAT.MISMATCH report
3. The output of the following list commands.

>TERM 300

>LIST FXXX.EB.SYSTEM.SUMMARY AL.CCY.MKT AL.CCY AL.CCY.BAL.AMT AL.LCL.BAL AL.CCY.POSN AL.LCL.POS


AL.CCY.EXCEP AL.LCY.EXCEP AL.TOTAL.LCY PL.TOTAL.LCY EXCEPT.AMT.LCY BY.DSND @ID

>TERM 300

>LIST F.EB.JOURNAL.SUMMARY BY.DSND @ID NON.CONT.APP NC.DEBIT.TOT NC.CREDIT.TOT NON.CONT.TOT


NON.CONT.BALANCE

Note: Kindly replace XXX with mnemonic of the company.

Revaluation Errors / Currency differences


1. Full view of latest EB.SYSTEM.SUMMARY record

2. The output of the following list commands.

>TERM 300

>LIST FXXX.EB.SYSTEM.SUMMARY AL.CCY.MKT AL.CCY AL.CCY.BAL.AMT AL.LCL.BAL AL.CCY.POSN AL.LCL.POS


AL.CCY.EXCEP AL.LCY.EXCEP AL.TOTAL.LCY PL.TOTAL.LCY EXCEPT.AMT.LCY BY.DSND @ID

If the problematic date adn currency is known then the below listings required from post cob of the problematic date

jsh->TERM 600

jsh ->LIST FXXX.POS.MVMT.HIST WITH BOOKING.DATE EQ <<DATE>> AND CURRENCY EQ <<CCY>> VALUE.DATE
TRANS.REFERENCE TRANSACTION.CODE EXCHANGE.RATE AMOUNT.LCY AMOUNT.FCY SYSTEM.ID NOPAGE

jsh ->LIST FXXX.RE.CONSOL.SPEC.ENTRY WITH BOOKING.DATE EQ <<DATE>> BY @ID TRANS.REFERENCE


TRANSACTION.CODE VALUE.DATE TOTAL AMOUNT.LCY TOTAL AMOUNT.FCY CONSOL.KEY.TYPE CONTIG SYSTEM.ID
CURRENCY NOPAGE

jsh ->LIST FXXX.STMT.ENTRY WITH BOOKING.DATE EQ <<DATE>> BY @ID TRANS.REFERENCE TRANSACTION.CODE


VALUE.DATE TOTAL AMOUNT.LCY TOTAL AMOUNT.FCY ACCOUNT.NUMBER SYSTEM.ID CURRENCY NOPAGE

Where

DATE => Problematic day

CCY => Problematic currency

jsh->LIST Fxxx.POSITION AMOUNT.1 AMOUNT.2 LCY.AMOUNT SYSTEM.DATE SD.AMOUNT.1 SD.AMOUNT.2


SD.LCY.AMOUNT NOPAGE

When there are no mismatches


In certain cases where there are no mismatches, there is a possibility that the contract details may not match with the reported amount
(CRB). In such cases RE.CONTRACT.DETAIL\EB.CONTRACT.BALANCES should be provided in addition to the listings (SPEC,
STMT, CATEG) and contract history.

Entries not as expected


 Relevant section from the TRANS.JOURNAL(TRANS.JOURNAL2 –Prior to R8 / TXN.JOURNAL.PRINT – From R8) report.

73 PACS
Support Handbook

 Print of the deal record.


 Print of the STMT.ENTRY and/or CATEG.ENTRY records.

The key for these will be found in the STMT.NO field on the deal. The first multi-field contains the main number; the second has the
range of numbers on the STMT.ENTRY file and the third the range of numbers on the CATEG.ENTRY file.

103. 1 STMT.NOS....... 1036875794.00

103. 2 STMT.NOS....... 1-2

103. 3 STMT.NOS....... 1

Means that for STMT.ENTRY file there are records 1036875794.000001 and 1036875794.000002, and for CATEG.ENTRY there is
record 1036875794.000001.

If the problem arose yesterday then the records from CONSOL.ENT.LWORK.DAY could be required, extract records where the field
TXN.REF (2) is equal to the deal number.

Also provide us the RE.CONSOL.SPEC.ENTRY listing if the problem is relating to contract level update.

Issues in CRB report


The below information required for any issues in CRB report

1. jshow -c RE.OUTPUT.EXTRACT

2. Full view of RE.EXTRACT.PARAMS of the report

3. Full view of RE.RETURN.EXTRACT of the report

4. Below listings

jsh->TERM 600

jsh->LIST Fxxx.RE.CRF.<<report.name>> CURRENCY LOCAL.BALANCE FOREIGN.BALANCE DEAL.BALANCE


DEAL.LCY.BALANCE DEAL.VALUE.DATE DEBIT.MVMT DEBIT.LCY.MVMT CREDIT.MVMT CREDIT.LCY.MVMT NOPAGE

jsh->TERM 600

jsh ->SELECT Fxxx.EB.CONTRACT.BALANCES WITH CONSOL.KEY LIKE <<CAL.KEY>>...

jsh ->LIST Fxxx.EB.CONTRACT.BALANCES TYPE.SYSDATE OPEN.BALANCE CREDIT.MVMT DEBIT.MVMT CURR.ASSET.TYPE


OPEN.ASSET.TYPE PREV.ASSET.TYPE DATE.LAST.UPDATE CO.CODE NOPAGE

jsh->TERM 600

jsh->SELECT Fxxx.RE.STAT.LINE.BAL LIKE <<report.name>>...<<CCY>>...<<date>>...

jsh->LIST Fxxx.RE.STAT.LINE.BAL OPEN.BAL OPEN.BAL.LCL CR.MOVEMENT CR.MVMT.LCL DB.MOVEMENT DB.MVMT.LCL


CLOSING.BAL CLOSING.BAL.LCL NOPAGE

RCA Entry
1. Full CRF detailed report

2. Full Mismatch report

3. Below listing

jsh->TERM 600

jsh ->LIST Fxxx.RE.STAT.LINE.BAL WITH @ID LIKE ...<date>... OPEN.BAL OPEN.BAL.LCL CR.MOVEMENT CR.MVMT.LCL
DB.MOVEMENT DB.MVMT.LCL CLOSING.BAL CLOSING.BAL.LCL NOPAGE

Enquiry CATEG.ENT.BOOK issue


1. Full view of ACCOUNT.PARAMETER

Locking in ENT.KEY.WORK files


1. Full view of ACCOUNT.PARAMETER

74 PACS
Support Handbook

2. Full view of SPF record

Performance issue on LINE.BAL/ LINE.MVMT jobs


1. Full COMO of the jobs

2. Full view of the SPF record

3. Full view of batch records BNK/RE.BUILD.SLC, BNK/RE.UPDATE.SLC.LINE.BAL, BNK/RE.PRINT.DEAL.RPT

4. Below counts

jsh->COUNT Fxxx.RE.STAT.LINE.BAL

jsh->COUNT Fxxx.RE.STAT.LINE.MVMT

Catch ALL issues


1. Full view of CRF detailed report

2. Full view of RE.STAT.REP.LINE, RE.STAT.RANGE

3. jsh -> LIST F.RE.REP.LINE.CALCULATE

4. Full view of CONSOLIDATE.COND records

Post Closing
PC adjustment is not reflecting in Report

1. Full view of the PC.PERIOD record.

2. Full view of the PC.UPDATE.REQUEST record

3. Sample adjustment transaction by FT / DC which is to adjust the report line balance in PC report

4. Full view of the entry record updated in STMT.NOS of the FT record

5. COMO of the service XXX/PC.UPDATE.REQUEST

6. DETAILED movement type LIVE CRF/CRC report as at the close of PC period open date

7. DETAILED movement type PC CRF/CRC report as at the close of PC period open date

8. Full view of RE.STAT.REQUEST / RE.CONSOL.REQUEST record which is used for generating CRF/CRC report.

9. Full view of SPF record.

PC Database is not created in System

1. Full view of PC.PERIOD record

2. Full view of BATCH record for XXX/PC.CREATE.DATABASE

3. COMO of the batch XXX/PC.CREATE.DATEBASE

4. Full view of SPF record.

5. Output of below commands,

a. >SELECT F.FILE.CONTROL WITH PC.FILE EQ 'Y'

6. >LIST F.FILE.CONTROL ONLY

a. ->SELECT F.FILE.CONTROL LIKE ...PC<DATE>...

>LIST F.FILE.CONTROL ONLY

C) ->SELECT VOC LIKE ...PC<DATE>...

>LIST-ITEM VOC

75 PACS
Support Handbook

Securities
CORPORATE ACTIONS
Provide records from the following files:
 SC.PARAMETER
 SC.CA.PARAMETER
 SECURITY.MASTER
 DIARY.TYPE
 DIARY
 ENTITLEMENT
 REDEMPTION.DET
 REDEMPTION.CUS
 DIV.COUP.DET
 DIV.COUP.CUS
 SECURITY.TRANS
 SECURITY.POSITION
 SC.ENT.AUTHORISE
 SC.SETTLEMENT
 COUPON.TAX.CODE
 TAX
 CONCAT FILES LIKE SC.CON.ENTITLEMENT SC.ENT.WORK SC.ENT.WORK.POST SC.DIA.REV.WORK CONCAT.DIARY

If the problem is related to


1) Creation of any Entitlements, respective SECURITY.POSITION.

2) Creation of Entitlements while doing through Phantom/Service (available from T24) even if the SECURITY.POSITION exist, then

 a. Service, TSA.SERVICE - SC.CORPORATE.ACTIONS and the corresponding COMO


 b. Corresponding OFS.REQUEST.DETAIL record from the log file specified in the related OFS.SOURCE.

3) For all calculation related problems;

 a. Specification of business requirement and clients own calculation of the problematic amount / amounts.

4) Balance Mismatch, then all the a/c entries (RE.CONSOL.SPEC.ENTRY, STMT.ENTRY, CATEG.ENTRY). (Format has been
specified in section 2.1 Balance Mismatch Messages of Chapter 2 Accounting and Reporting)

ET(EU SAVINGS DIRECTIVE)


Provide records from the following files:
 EU.ALLOCATION.DETS
 EU.DATA.BUILD
 EU.TAX.LINK
 EU.TAX.PARAM
 INT.MOVEMENT.PARAM
 EU.TXN.BASE (from the back end)
 SEC.TRADE
 SECURITY.TRANSFER

76 PACS
Support Handbook

 POSITION.TRANSFER
 DIARY
 ENTITLEMENT
 SECURITY.MASTER
 CUSTOMER
 TXN.TAX.CODE
 TX.TXN.BASE.PARMS
 TX.TXN.BASE.MAPPING
 TAX.TYPE
 CONDITION.PRIORITY
 TAX.GEN.CONDITION
 CUSTOMER.CHARGE
 TAX

Securities
Note: Please download the T24.SECURITIES.INFO tool from https://tcsp.temenos.com/Pages/ToolsnUtil.aspx to automatically fetch
Securities module related data that helps for analysis of issues.

Please note that T24.SECURITIES.INFO uses EB.PRINT.RECORD which is part of “Info Extractor”. Kindly install “Info Extractor”
for having EB.PRINT.RECORD before installing T24.SECURITIES.INFO

GENERAL ISSUES
Provide records from the following files:

For Parameter set-up (Where ever applicable)


 SC.PARAMETER
 ACCOUNT.PARAMETER
 SC.STD.SEC.TRADE
 SC.GROUP.PARAM

For Trading and Orders related problems (where ever applicable)


 SEC.TRADE
 SECURITY.MASTER
 SEC.ACC.MASTER
 SECURITY.TRANSFER
 POSITION.TRANSFER
 SEC.OPEN.ORDER
 SC.EXE.SEC.ORDERS
 SC.SETTLEMENT
 SECURITY.POSITION
 SECURITY.TRANS
 SC.BLOCK.SEC.POS
 PORTFOLIO.CONSTRAINT
 SC.SECURITY.CONSTAINT
 SC.SUB.ACC.ROUTING
 SC.CU.DEPO.DEFAULT

77 PACS
Support Handbook

 SC.GROUP.ORDERS
 SCTR.GROUP.CONDITION
 ORDER.BY.CUST
 CUSTOMER.CHARGE
 STOCK.EXCHANGE
 STK.EXC.LOCAL
 PRICE.TYPE
 CONCAT FILES LIKE TRN.CON.DATE, TRN.CON.TRADE.DATE, TRN.CON.VALUE.DATE, SC.VAL.POSITIONS,
SC.SETTL.DATE.CONTROL, SC.SETTLE.TXNS, SC.SETTLE.CUST, SC.SETTLE.BROK SECS.UNAUTH SC,GRP.ORD.WRK
(WHERE EVER APPLICABLE)
 CUSTOMER.SECURITY
 PERIODIC.INTEREST
 RELATED BATCH RECORDS LIKE SC.BATCH.APP (IF APPLICABLE)
 SC.STD.POS.TRANSF
 SC.DEL.INSTR
 SEC.DEL.CONTROL
 DE.MAPPING, DE.MESSAGE, DE.ADDRESS
 SP.STP.PARAM (for Straight Through Processing module - SP)
 EB.PHANTOM (IF APPLICABLE)
 OFS.SOURCE (IF APPLICABLE)
 SC.POS.ASSET
 ALL ACCOUNTING ENTRIES LIKE STMT.ENTRY, CATEG,ENTRY, RE.CONSOL.SPEC.ENTRY, CONSOL.ENT.TODAY
 CAL RECORD

For problems relating to Own Book portfolios (Where ever applicable)


 SEC.ACC.MASTER
 SECURITY.MASTER
 SECURITY.TRANS
 SECURITY.POSITION
 SC.TRADING.POSITION
 SC.TRADE.POS.HISTORY
 SC.TRANS.POS.HISTORY
 Related CAL record associated in STP
 EB.CONTRACT.BALANCES of STP
 All STMT.ENTRY ,CATEG.ENTRY and RE.CONSOL.SPEC.ENTRY for the transaction
 RE.CONSOL.SEC
 MISMATCH REPORT
 TRANSACTION.JOURNAL
 GL AND PL REPORTS
 CONSOL.ENT.TODAY

Balance Mismatch in SC:


Apart from the above details mentioned under “For problems relating to Own Book portfolios kindly also provide us with details as
referred under - Refer to listing mentioned in section 2.1 Balance Mismatch Messages of Chapter 2, Accounting and Reporting

78 PACS
Support Handbook

 For Modelling related problems


 POLICY.PARAMETER
 INVESTMENT.PROGRAM
 SEC.ACC.MASTER
 SC.PORT.COMPARE
 SC.GROUP.COMPARE
 SEC.OPEN.ORDER

For Valuation related problems (Where ever applicable)


 SC.POS.ASSET
 SECURITY.MASTER
 SECURITY.TRANS
 SC.VALUATION.EXTRACT
 CONCAT FILES SC.VAL.POSITIONS, SC.POS.MOVEMENT, VAL.INTERFACE, ASSET.BREAK
 SCM.SUB.ASSET.CHG.TODAY
 SUB.ASSET.TYPE
 ASSET.TYPE
 SC.PERF.DETAIL
 For Performance Reporting related problems
 TRANS.FUND.FLOW
 SC.CASH.FLOW.TRANS
 SC.PERF.DETAIL

For Safe Custody and Advisory Fee related problems


 SAFECUSTODY.VALUES
 SEC.ACC.MASTER
 CUSTOMER.CHARGE
 SCSK.GEN.CONDITION
 SCSK.GROUP.CONDITION
 SCSF.CHARGE.PARAMETER
 SCPM.GEN.CONDITION
 SCPM.GROUP.CONDITION
 SCPM.CHARGE.PARAMETER
 FT.COMMISSION.TYPE
 SAFECUSTODY.EXTRACT
 SC.SAFEKEEP.ACTIVTY
 SC.ADV.FEES.ACTIVITY
 SC.ASSET.BAL
 SAFEKEEP.HOLDING
 SC.ADVISORY.CHG
 SC.SAFE.FEES.POST
 SC.ADV.FEES.POST
 SC.PARAMETER

79 PACS
Support Handbook

 BATCH RECORD SC.SYS.END.OF.DAY


 Como record generated by SC.SAFE.FEES.POST / SC.ADV.FEES.POST in case of the problem related to posting of fees.

For Trailer Fees related problems


 SC.TR.FEE.PARAMETER
 SC.TRAIL.FEES.ARRANGEMENT
 SC.TRAIL.FEES.EXTRACT
 SC.TRAIL.FEES.HOLDING

Custodial Operations
 VAULT.PARAMETER
 VAULT.EXPECT
 VAULT.CONTROL
 Concat file FXXX.VAULT.CERTS (Where XXX is the company mnemonic)
 Related transactions i.e. SEC.TRADE , SECURITY.TRANSFER or POSITION.TRANSFER which created VAULT.EXPECT

Wealth Reporting (WR)


 WR.PARAMETER.
 PDF record of the problematic portfolio.
 CSV files for the problematic portfolio.
 Full view of the problematic enquiry

Wealth Reporting Orchestrate (WR-OR)


 T24 CSV files.
 Format Files.
 Report and Datamap Export.
 Structures of tables available in T24 SourceData database.

STANDING.ORDER
For all problems
Provide screen dumps of the following records

 STO record
 STMT.ENTRY record
 CATEG.ENTRY record
 ACCT.ACTIVITY records for involved accounts
 FT.APPL.DEFAULT
 FT record
 HOLIDAY record

Problem in STO processing:


Provide screen dumps of the following records

 STO record
 EXCEPTION.LOG.FILE or EXCEPTION.LOG.HIST record for that STO generated during EOD/COB.
 FT.APPL.DEFAULT

80 PACS
Support Handbook

 LIST FXXX.STO.FREQ.DATE
 COMO for the batch that process STO
 HOLIDAY record

T24.PAYMENTS.INFO
The tool T24.PAYMENTS.INFO can be used to extract STO related files:

The tool and the user guide is available in the link https://tcsp.temenos.com/Pages/ToolsnUtil.aspx

Files extracted using the tool:


 STANDING.ORDER
 ACCOUNT
 ACCOUNT ACTIVITY
 COMPANY
 FT.APPL.DEFAULT
 FT.CHARGE.TYPE
 FT.COMMISSION.TYPE
 STO.FREQ.DATE
 RESUBMITTED STO
 FUNDS TRANSFER
 HOLIDAY

81 PACS
Support Handbook

Structured Products
The following basic details need to be provided for all issues based on the problem faced.

 SY.PARAMETER
 SY.PRODUCT
 SY.PRODUCT.DEFINITION
 SY.PRODUCT.DESCRIPTION
 SY.PRODUCT.INTERFACE
 SY.CUSTOMER
 SY.PORTFOLIO

Problem related to Event processing


 SY.DCD
 SY.EVENT.DEFINITION
 SY.EVENT
 SY.TRANSACTION
 SY.UNIT.DEFINITION
 SY.UNIT
 SY.TXN.LINK
 SY.CONTRACT.LINK

Problem related to Transaction processing


 SY.TRANSACTION
 SY.DCD or Customized version

Syndicated Loans
Balance mismatch in SL - TAFC Compliance
For balance mismatch, supply us with details of

 STMT.ENTRY, CATEG.ENTRY and RE.CONSOL.SPEC.ENTRY.


 (Refer to listing mentioned in section 2.1 Balance Mismatch Messages of Chapter 2, Accounting and Reporting.)
 SL.FACI.PART.BALANCES of own participant
 SL.LOAN.PART.BALANCES of own participant

Balance mismatch in SL - TAFJ Compliance


For balance mismatch, supply us with details of

 STMT.ENTRY, CATEG.ENTRY and RE.CONSOL.SPEC.ENTRY.


 >TERM 500
 LIST Fxxx.STMT.ENTRY WITH TRANS.REFERENCE LIKE ...SL.ID... TRANS.REFERENCE TRANSACTION.CODE TOTAL
AMOUNT.LCY TOTAL AMOUNT.FCY EXCHANGE.RATE CURRENCY BOOKING.DATE VALUE.DATE
ACCOUNT.NUMBER SYSTEM.ID
 LIST Fxxx.RE.CONSOL.SPEC.ENTRY WITH TRANS.REFERENCE LIKE ...SL.ID... @ID BOOKING.DATE VALUE.DATE
TRANSACTION.CODE TOTAL AMOUNT.LCY EXCHANGE.RATE TOTAL AMOUNT.FCY CURRENCY
TRANS.REFERENCE CONSOL.KEY.TYPE SYSTEM.ID ID.SUP
 LIST Fxxx.CATEG.ENTRY WITH OUR.REFERENCE LIKE ...SL.ID... PL.CATEGORY TOTAL AMOUNT.LCY TOTAL
AMOUNT.FCY EXCHANGE.RATE OUR.REFERENCE BOOKING.DATE VALUE.DATE SYSTEM.ID CURRENCY ID.SUP

82 PACS
Support Handbook

 Replace XXX WITH COMPANY Mnemonic.

For all SL Problems:


Provide screen dumps from the following files:

 PRE.SYNDICATION.FILE
 FACILITY
 SL.LOANS
 SL.PARAMETER

Problem with Balances


 SL.FACI.BALANCES
 SL.FACI.PART.BALANCES
 SL.LOAN.BALANCES
 RE.CONTRACT.BALANCES
 SL.LOAN.BALANCES.HIST
 SL.LOAN.PART.BALANCES.HIST
 SL.FACI.BALANCES.HIST
 SL.FACI.PART.BALANCES.HIST
 STMT.ENTRY, CATEG.ENTRY and RE.CONSOL.SPEC.ENTRY.

Problem with Repayment of Loan


 SL.REPAYMENT.SCHEDULES
 SL.LOAN.SCHEDULES
 SL.FACI.SCHEDULES
 SL.LOANS.SCHEDULES.PAST
 SL.FACI.BALANCES
 SL.LOAN.BALANCES
 STMT.ENTRY, CATEG.ENTRY and RE.CONSOL.SPEC.ENTRY.
 FACILITY.REPAY.SCHEDULES
 SL.REPAY.SCHEDS
 SL.LOAN.ACCR.DETAILS
 SL.FACI.ACCR.DETAILS

Problem With Updates In Facility:


 PRE.SYNDICATION.FILE
 FACILITY
 SL.FACI.BALANCES

Problem with SL.ROLLOVER


 FACILITY
 SL.FACI.BALANCES
 SL.ROLLOVER
 SL.FACI.PART.BALANCES

83 PACS
Support Handbook

Problem with SL.BUY.SELL


 FACILITY
 SL.BUY.SELL
 SL.FACI.BALANCES
 SL.FACI.PART.BALANCES

Problem with overdues


 FACILITY
 SL.OD.DUES
 SL.LOAN.BALANCES
 SL.LOAN.PART.BALANCES
 STMT.ENTRY, CATEG.ENTRY and RE.CONSOL.SPEC.ENTRY.

Problem with Charges


 FACILITY
 SL.CHARGE
 SL.CHARGE.ACTIVITY
 SL.CHARGE.BALANCES
 SL.LOAN.BALANCES
 SL.LOAN.PART.BALANCES

84 PACS
Support Handbook

System Core
System Core - TAFJ Compliance
Any TAFJ related issues, our first requests are as follows.

1. TAFJ.properties – To know the current settings and path

2. TAFJTrace.properties – to know about the logs enabled/disabled and request for enabling/disabling.

3. Default.properties - To know which configuration file is being used.

4. Full view of the F.SPF>SYSTEM record to know the current release and list of updates installed so far

5. >tVersion or >tVersion –cf tafj.properties to know the current TAFJ Version

6. >tdiag or >tDiag –cf tafj.properties to know the overall settings of the system

ALTERNATE KEY issues - TAFC Compliance


 Full view of USER record
 Screenshots explaining the problem.
 Full view of Company record
 Full view of the corresponding application record from EB.ALTERNATE.KEY
 From the jshell prompt
 jshow -c UPDATE.ALT.KEY.CONCAT IN2ALTKEY VALIDATE.ALTKEY

jsh -->CT F.XXX.YYY Record Id

Where XXX is Name of the Application in which EB.ALTERNATE.KEY is set

Where YYY is Name of the Field in which EB.ALTERNATE.KEY is set

(Record ID is the ID to which record is mapped using EB.ALTERNATE.KEY

ALTERNATE KEY issues - TAFJ Compliance


 Full view of USER record
 Screenshots explaining the problem.
 Full view of Company record
 Full view of the corresponding application record from EB.ALTERNATE.KEY
 $tShow UPDATE.ALT.KEY.CONCAT IN2ALTKEY VALIDATE.ALTKEY
 Full view of the problematic Record ID from FXXX.YYY

Where XXX is Name of the Application in which EB.ALTERNATE.KEY is set

Where YYY is Name of the Field in which EB.ALTERNATE.KEY is set

(Record ID is the ID to which record is mapped using EB.ALTERNATE.KEY

COB/EOD Error
The following information is required at the point of COB/EOD error for our initial analysis. Subsequent information can be
communicated to Temenos as per requisition from 24/7 Support Team.

Preliminary details irrespective of Globus/T24 release - TAFC Compliance


 Name of the Bank
 Contact number
 Globus/T24 Release & Database used (jBASE / Universe / Oracle)

85 PACS
Support Handbook

 EOD/COB started time


 Total EOD/COB duration time
 Normal EOD/COB completion time
 Whether the EOD is run from Desktop or Telnet. If T24, then number of agents. If Desktop, then number of sessions.
 The specific job name and BATCH record name.
 The batch and the job that has crashed by executing the following commands:

LIST F.BATCH WITH PROCESS.STATUS EQ 1 JOB.NAME JOB.STATUS

LIST F.BATCH WITH PROCESS.STATUS EQ 3 JOB.NAME JOB.STATUS

LIST F.BATCH WITH PROCESS.STATUS EQ 4 JOB.NAME JOB.STATUS

 A screen print of the error message.


 Print of any deal/account/limit records where an id has been printed as part of the error message.
 The system run date.
 Whether the system is a single or multi-company set-up.
 A full print of the COMO for the failed process.
 Information about anything special that has happened, e.g. System ran out of disk space.

Information Specific to Globus/T24 Release - TAFC Compliance

For Globus Release below G13.2.07:


1. If the EOD is run from Telnet then fetch the full COMO of the batch where the EOD has crashed. This can be obtained from the
Universe/jBASE prompt:

>CT &COMO& BAT.<<Company.mnemonic>>_<<Process Name>>

Eg: BAT.BNK_LD.END.OF.DAY

To get the Process Name, eliminate “<<Company.Mnemonic>>/ “if present, from the BATCH record id.

Note: The batch process that has crashed can be obtained from the above set of commands where the PROCESS.STATUS is set to 3 or
4.

2. If the EOD is run from Desktop, check how many sessions are used. It can be obtained from the field BATCH.SESSIONS in the SPF
application.

27 HELD.RPT.RETENTION 5

28 CACHE.SIZE........ 500

30 PREVIOUS.RELEASE.. G11.1.02

32 BATCH.SESSIONS.... 10

35. 1 NON.2DEC.CCY... BEF

In order to extract the thread COMO for each of the individual session, execute the below command from Universe/jBASE prompt

>CT &COMO& BAT.nn

Eg: >CT &COMO& BAT.1

where nn = 1 to Number of BATCH SESSIONS.

3. The batch COMO may also be extracted by running the main line routine MERGE.GUI.COMO from the Awaiting Application
prompt.

The COMO may be extracted as below

>CT &COMO& BAT. <<Company.Mnemonic>>_<<Process Name>>

Eg: >CT &COMO& BAT.BNK_SYSTEM.END.OF.DAY3

To get the Process Name, eliminate “<<Company.Mnemonic>>/ ” if present, from the BATCH record id.

86 PACS
Support Handbook

For Globus Release G13.2.07


▪ In addition to the above information, we also require the following details.

▪ F.BATCH.STATUS record for the crashed batch process. The id of the F.BATCH.STATUS record will be of the format.

>CT F.BATCH.STATUS <<BATCH-JOB.NAME-JOB.POSITION>>

Example:
>CT F.BATCH.STATUS SYSTEM.END.OF.DAY3-PROC.REVAL.STATIC.CHANGE-1

SYSTEM.END.OF.DAY3-PROC.REVAL.STATIC.CHANGE-1

0001 processed

>

 Check the job list the job is using. This info is maintained in the file F.LOCKING with the same id format as that of
F.BATCH.STATUS,

BATCH.NAME-JOB.NAME-JOB.POSITION. The format of the job list file name is Fxxx.JOB.LIST.Y (xxx- Company Mnemonic, Y –
the session number which has run the select routine)

>CT F.LOCKING SYSTEM.END.OF.DAY3-PROC.REVAL.STATIC.CHANGE-1

SYSTEM.END.OF.DAY3-PROC.REVAL.STATIC.CHANGE-1

0001 FBNK.JOB.LIST.4

>

 The ERROR record in F.BATCH.STATUS.

Eg :

>CT F.BATCH.STATUS ERROR

ERROR

0001 AC.STMT.UPDATE*PRINT.ACCOUNT.STMT

▪ The respective EB.EOD.ERROR details.

LIST F.EB.EOD.ERROR WITH @ID LIKE …<<date when the crash had occurred>>…

For Globus Release T24 R4 onwards:


1. Number of agents (tSAs) used for running the COB.
2. Full COMO of the crashed agent. This can be obtained from the file F.TSA.STATUS in the field COMO.NAME
3. Screen shot of F.TSA.STATUS of the crashed agent

CURRENT.SERVICE. COB

NEXT.SERVICE.... STOP

LAST.MESSAGE.... _MTA/STARTUP_EB.PRINT_4_04 JUN 2005_12:37:30_Processing...1 C

COMO.NAME....... tSA_4_1367043998

JOB.PROGRESS.... 3

The COMO can be fetched from the jBASE prompt as:

Jsh liveàCT &COMO& tSA_4_1367043998

The respective EB.EOD.ERROR details.

LIST F.EB.EOD.ERROR WITH @ID LIKE …<<date when the crash had occurred>>…

SHOW-ITEM-LOCKS (This can be obtained from jsh Eg: jsh--àSHOW-ITEM-LOCKS)

87 PACS
Support Handbook

Preliminary details irrespective of Globus/T24 r elease - TAFJ Compliance


 Name of the Bank
 Contact number
 T24 Release & Database used (SQL / Oracle/DB2)
 TAFJ.properties file
 COB started time
 Total COB duration time
 Normal COB completion time
 Whether the COB is run using Telnet session using tRun START.TSM manually or by executing the servlets.
 The specific job name and BATCH record name.
 Full view of the output generated using BASIC.LISTING with option 5.
 A screen print of the error message.
 Print of any deal/account/limit records where an id has been printed as part of the error message.
 The system run date.
 Whether the system is a single or multi-company set-up. To confirm the same please send us the full view of the
TSA.SERVICE>COB and TSM record.
 A full print of the COMO for the failed process can be extracted from &COMO& directory specified in the
temn.tafj.runtime.directory.current path.
 Information about anything special that has happened, e.g. System ran out of disk space.

Information Specific to TAFJ-T24 Release R09 onwards


1. Number of agents (tSAs) used for running the COB. Full view TSA.WORKLOAD.PROFILE record attached in the TSA.SRVICE>COB

2. Full COMO of the crashed agent. This can be obtained from the file F.TSA.STATUS in the field COMO.NAME

3. Screen shot of F.TSA.STATUS of the crashed agent

CURRENT.SERVICE. COB

NEXT.SERVICE.... STOP

LAST.MESSAGE.... _MTA/STARTUP_EB.PRINT_4_04 JUN 2005_12:37:30_Processing...1 C

COMO.NAME....... tSA_4_1367043998

JOB.PROGRESS.... 3

The COMO can be fetched from the &COMO& directory in the temn.tafj.runtime.directory.current specified in the TAFJ.properties
file.

4. The respective EB.EOD.ERROR details.

Constraints Processing - TAFC Compliance


 Full view of SPF record
 Full view of EB.GC.CONSTRAINTS record
 Source code of ROUTINES if attached to EB.GC.CONSTRAINTS record
 EB.GC.PARAMETER record with ID as the respective company id or SYSTEM.
 EB.GC.ACTIVE record for the corresponding application
 Full view of EB.GC.GLOBAL record
 Full view of the corresponding COMPANY record
 jsh->jshow -c EB.GC.CHECK.CONSTRAINT
 Screenshots explaining the problem.

88 PACS
Support Handbook

 Corresponding USER record

Constraints Processing - TAFJ Compliance


 Full view of SPF record
 Full view of EB.GC.CONSTRAINTS record
 Source code of ROUTINES if attached to EB.GC.CONSTRAINTS record
 EB.GC.PARAMETER record with ID as the respective company id or SYSTEM.
 EB.GC.ACTIVE record for the corresponding application
 Full view of EB.GC.GLOBAL record
 Full view of the corresponding COMPANY record
 $tShow EB.GC.CHECK.CONSTRAINT
 Screenshots explaining the problem.
 Corresponding USER record

DM related issues - TAFC Compliance


Screenshots explaining the problem
 DM.APPLICATION.INFO record
 DOC.GEN.CONDITION record
 DOCUMENT.REQUIRED record
 DOCUMENT.CLASS record
 DOCUMENT.TYPE record
 CUST.DOCUMENT/TRANS.DOCUMENT records of that contract
 jshow -c DM.TRACKING.REQ

jshow -c DM.GET.LIST.DOCUMENTS

DM related issues - TAFJ Compliance


Screenshots explaining the problem
 DM.APPLICATION.INFO record
 DOC.GEN.CONDITION record
 DOCUMENT.REQUIRED record
 DOCUMENT.CLASS record
 DOCUMENT.TYPE record
 CUST.DOCUMENT/TRANS.DOCUMENT records of that contract
 tShow DM.TRACKING.REQ
 tShow DM.GET.LIST.DOCUMENTS

EB.DYNAMIC.ATTRIBUTES/EB.SWITCH.PARAMETER set up issues


 EB.DYNAMIC.ATTRIBUTES or EB.SWITCH.PARAMTER record.
 Local routines attached to EB.DYNAMIC.ATTRIBUTES
 SPF record
 Screenshots showing the problem.

89 PACS
Support Handbook

EB.EOD.ERROR for Mismatch in Position and Consolidation


1. Full view of latest EB.SYSTEM.SUMMARY record

2. Latest RE.STAT.MISMATCH report

3. The output of the following list commands.

>TERM 300

>LIST FXXX.EB.SYSTEM.SUMMARY AL.CCY.MKT AL.CCY AL.CCY.BAL.AMT AL.LCL.BAL AL.CCY.POSN AL.LCL.POS


AL.CCY.EXCEP AL.LCY.EXCEP AL.TOTAL.LCY PL.TOTAL.LCY EXCEPT.AMT.LCY BY.DSND @ID

>TERM 300

>LIST F.EB.JOURNAL.SUMMARY BY.DSND @ID NON.CONT.APP NC.DEBIT.TOT NC.CREDIT.TOT NON.CONT.TOT


NON.CONT.BALANCE

Note: Kindly replace XXX with mnemonic of the company.

EB.TABLE.DEFINITION - TAFC Compliance


 EB.TABLE.DEFINITION record of the problematic application.
 Screenshots showing the problem
 PGM.FILE of the corresponding application
 EB.TABLE.PROCEDURES record (if the problem is with field validations or cross validations)
 If problem is with file creation, VOC, jstat of the corresponding file.

EB.TABLE.DEFINITION - TAFJ Compliance


 EB.TABLE.DEFINITION record of the problematic application.
 Screenshots showing the problem
 PGM.FILE of the corresponding application
 EB.TABLE.PROCEDURES record (if the problem is with field validations or cross validations)
 If problem is with file creation, please use DBTools>JQL>USAGE (F.SPF is given for sample)

a. GETDBNAME F.SPF

b. DESCRIBE F_SPF

c. DESCRIBE D_F_SPF

d. DESCRIBE TAFJV_F_SPF

Enquiries - TAFC Compliance


 Does the problem occur only on a particular enquiry, or, for all enquiries? Problem with newly created enquiry or it happens
after upgrade? Whether problem with core enquiry or local enquiry?
 Full view of the ENQUIRY record with all the attached routines
 The same enquiry output from Classic
 Communication log
 jshow of S.ENQUIRY.SELECTION, S.NEXT.ENQUIRY.PAGE, ENQ.BUILD.PAGE, S.ENQUIRY.DOWN
 If the problem is occurring in case of drill down enquiries, check if the same happens performing the same action/operation
from command line.
 Versions
 Was the version created using Screen designer or Version application.
 Problem with newly created version or it happens after upgrade?
 Full view of VERSION record, along with screenshots of the version;

90 PACS
Support Handbook

 Instance of the problem along with screenshots;

Enquiries - TAFJ Compliance


 Does the problem occur only on a particular enquiry, or, for all enquiries? Problem with newly created enquiry or it happens
after upgrade? Whether problem with core enquiry or local enquiry?
 Full view of the ENQUIRY record with all the attached routines
 tShow of S.ENQUIRY.SELECTION, S.NEXT.ENQUIRY.PAGE, ENQ.BUILD.PAGE, S.ENQUIRY.DOWN
 If the problem is occurring in case of drill down enquiries, check if the same happens performing the same action/operation
from command line.
 Versions
 Was the version created using Screen designer or Version application.
 Problem with newly created version or it happens after upgrade?
 Full view of VERSION record, along with screenshots of the version;
 Instance of the problem along with screenshots;
 If the ENQUIRY does not give expected results, please replicate the problem and get us the below logs.

a. Database.log

b. Runtime.log

c. Execute.log

d. Sqltrace.log

Design Studio - TAFC Compliance


• Full view of SPF record.

• Full view of OFS.SOURCE record DS.TELNET

• Full view of DS.PARAMETER record and corresponding VERSION record full view attached to the field VERSION.NAME.

• Corresponding DSL.MAPPING record. I.e full view of DSL.MAPPING ENQUIRY record in case the request is for ENQUIRY.

• Metadata .log file in case of any error while import/export data to T24 from Design Studio.

• Design Studio version and plugin version.

• Server.properties file available inside conf of <project>-server

• Output of corresponding resource screenshot from source tab. Example .version in case the issue is with importing/exporting Version
record.

Design Studio - TAFJ Compliance


 Full view of SPF record.
 Full view of OFS.SOURCE record DS.TELNET
 Full view of DS.PARAMETER record and corresponding VERSION record full view attached to the field VERSION.NAME.
 Corresponding DSL.MAPPING record. I.e full view of DSL.MAPPING ENQUIRY record in case the request is for ENQUIRY.
 Metadata .log file in case of any error while import/export data to T24 from Design Studio.
 Design Studio version and plugin version.
 Server.properties file available inside conf of <project>-server
 Output of corresponding resource screenshot from source tab. Example .version in case the issue is with importing/exporting
Version record.

T24 Web Services


The following would be the mandatory details for all TWS issues.

91 PACS
Support Handbook

These are the basic information required.

1)The TWS flavour used, i.e. TWS(EE) or TWS(.NET)

Issue TWS(EE)
1. plugin version of TWS(EE) used

2. Full view of SPF record.

3. Following information required in case the issue in creating the TWS project(war file)

Metadata .log file available in the project workspace.

Full view Enquiry/Version record used and the corresponding PW.ACTIVITY and

EB.SERVICE record from T24

4. Clear the TAFC\log directory, replicate the issue and send us the newly created TAFC\log.

4. The TWS war file created

6. In case jboss is used, The t24-ds.xml file from the <jboss installation directory>\server\default\deploy> folder

7. In case jboss is used, the jboss log file from the <jboss installation directory>\server\default\log> folder and the corresponding
application server log if other than jBoss.

8. Full view of OFS SOURCE record attached to the resource Adaptor.

9. Capture the OFS request in the server/application log and process the same using tSS and send us the output.

>tSS <OFS SOURCE used for TWS>

Issue in TWS(.NET)
1. The version of TWS(.NET) used and Visual Studio Version.

2. b)LIST F.SPF from jshell prompt

3. b)The log files from both project log and T24ServiceConnector log Folder

4. b) Detailed jbase_agent log (starting jbase_agent in –L mode)

5. b)connectors.xml file from conf directory of Service Connector

6.b)The enquiry/Version record used if problem faced in web service creation. Corresponding PW.ACTIVITY and

EB.SERVICE record from T24

Integration Framework - TAFC Compliance


Issue in creating/publishing event in T24 using EventDesigner(EE)

EventDesigner(EE) – Java

Full view of SPF record.

Integration plugin version used and IDE version.

Error message in the console window in case of issue in publishing the event to T24.

TAFC jagent log in case issue of in connecting/fetching T24 data in IDE(eclipse)

Integration Framework - TAFJ Compliance


Issue in creating/publishing event in T24 using EventDesigner(EE)

EventDesigner(EE) – Java

1. Full view of SPF record.

2. Integration plugin version used and IDE version.

92 PACS
Support Handbook

3. Error message in the console window in case of issue in publishing the event to T24.

4. TAFC jagent log in case issue of in connecting/fetching T24 data in IDE(eclipse)

EventDesigner(.NET)

1. Full view of SPF

2. Integration(.NET) plugin version and Visual Studio Version.

3. Error message in console window in case of issue in publishing the event to T24.

Issue in accessing the event in T24.

1.Full view of VERSION used to trigger the event.

2. Full view of corresponding IF.EXIT.POINTS

3. Full view of corresponding IF.INTEGRATION.FLOW.CATALOG from jsh.

4. Output from jsh prompt

Jsh>LIST-ITEM F.IF.INTEGRATION.FLOW.CATALOG ‘Deployed Event ID’

Full view of corresponding IF.EVENTS.INTERFACE.TABLE.

5.ESB used to trigger event from/to T24.

Enquiry - TAFC Compliance


 ENQUIRY record
 Print of the incorrect ENQUIRY output
 Prints of records from the file used in the ENQUIRY
 If it is a problem with the SELECT, then the output of the SELECT command from JBASE/Universe prompt.
 If problem with build routine or conversion routine, the routines attached.

Enquiry - TAFJ Compliance


• ENQUIRY record

• Print of the incorrect ENQUIRY output

• Prints of records from the file used in the ENQUIRY

• If it is a problem with the SELECT, then the output of the SELECT command from DBTools. You can use JQL2SQL tool to get us the
select executed from database level.

tafjr13@localhost:R13DB>JQL2SQL SELECT F.USER WITH @ID EQ INPUTTER

--------------------------------------------------------------------------------

DBTools JQL2SQL P1:1 C1:1

--------------------------------------------------------------------------------

SELECT RECID FROM "TAFJV_F_USER" WHERE RECID = ?

• If problem with build routine or conversion routine, the routines attached.

For access to universe / jBASE files


 A valid UNIX login and password, takes users directly to the universe / jBASE prompt.

This should be a different login name and password from that above in order for you to control access to your system.

Activate Passwords
Before the TEMENOS staff is expected or due to access your system:

 Set the passwords for Unix logins.

93 PACS
Support Handbook

 Activate T24 USER profiles by using History restore.


 Change the password using PASSWORD.RESET.
 `If supervision is required, ensure your staffs are available.

When TEMENOS staff arrives or connect:


 Advise them of login names, passwords and system availability.
 Network logon procedures.
 Printers available for use.
 Any unique site instructions.

If a TEMENOS consultant is on-site, they will require use of a PC, printer and telephone.

De-activate Password
When the TEMENOS staff leaves or disconnect:

 De-activate or change UNIX password.

De-activate T24 USER profiles by reversing the records.

For straight access to T24


A valid UNIX login and password, taking the user directly to the T24 sign on screen.

A unique USER profile set up especially for the TEMENOS staff with:

 Ability to use all applications with S(ee), P(rint), L(ist) and E(xception) functions for the companies in use. Other functions
need be provided as required for the analysis of the issue.
 Applications with a program type of ‘W’ with additional I(nput) and V(erify) functions.
 Default settings from a USER.SMS.GROUP.
 Restricted connect time(s).

jBASE Issues
Information Required for All Issues
 The output of the jBASE diagnostic utility. The command is jdiag –dvL
 (Output will be stored in jdiag.out. Please attach the jdiag.out file).
 Steps for replicating the problem along with screenshots.
 Whether the problem occurs in Classic, Desktop or Browser.
 The T24/ GLOBUS release in which the problem is reported.
 The Operating System details, with Maintenance Level details.

Problem relatin g to jBC statements and functions


 A sample routine used to recreate the problem and the output.
 Debugging information (if applicable) if sample routine could not be obtained,

jQL statement problems


 The output of the same jQL statement from jshell prompt
 Output of LIST-INDEX –a <filename>

Installation/jBASE Upgrade Issues


 The output of jdiag –dvL (output in jdiag.out), preferably run as root.
 The ‘remote.cmd’ (for NT) / ‘.profile’ (for Unix) file.

94 PACS
Support Handbook

 The ‘loginproc’ file and/ or ‘jprofile.bat’ (for NT);


 jBASE pack name which you are trying to install;

File Corruption issues


 Output of jstat –v on the corrupt file.
 Output of jrf –Rv on the corrupt file.
 Output of commands like COUNT, LIST or SELECT on the corrupt file.
 Output of jcheck –v run on the corrupt file, after taking the backup of the corrupt file.
 The corrupt file as a tarred, compressed (zipped in NT) attachment.
 Output of LIST <filename> *A9999

Note: jcheck and jrf are to be performed at a time when no other process is accessing the file.

Memory related issues


The output of command ulimit –a (UNIX only).

 The contents of the file ‘jBASE_error_trace’ from $JBCRELEASEDIR/tmp directory;


 If the problem is recreatable then the output of:4

• WHERE (V <port number of the session in which the problem is recreated>

• SHOW-ITEM-LOCKS

• truss –o truss.out –p <process id on the session where the problem is recreated> (Unix only)

• ps –ef | grep <Unix user running the application> (Unix only)

• mw42 -m

Note 1: All these details need to be collected in parallel when the problem is recreated.

Note 2: ‘truss’ command is available in selective Unix platforms only.

Binary/ Record Locking issues


WHERE (V <port number of the session in which the problem is recreated>

 SHOW-ITEM-LOCKS
 jRLA –dvL (if jRLA is running, in jBASE 4.1).
 jDLS –dvL (if running jDLS in multi-server architecture)
 ps –ef | grep <Unix user running the application> (Unix only).

jBASE spooler related issues

Output of commands
 SP-STATUS
 jsp_scan –v
 Status of printing from OS level

jBASE Licensing issues


 In jBASE 4.0, the output of

•jdiag –dvL (output in jdiag.out), run as root user only.

•jlicenseinfo –pt

 In jBASE 4.1, the output of

•jdiag –dvL (output in jdiag.out), run as root user only.

95 PACS
Support Handbook

•Details on whether jLicServer and jSlimServer is running.

A copy of ‘system.properties’ file from the ‘config’ directory of jBASE installation directory.

• jInstallKey -v

 In jBASE 5.0.x, the output of

• jInstallKey –v

• jdiag –dvL

• a copy of ‘system.properties’ file from $JBCRELEASEDIR/config directory

Transaction Journaling issues


 configuration details – whether standalone TJ or hot standby
 ‘jlogdup’ statements used
 Output of jlogadmin –V
 jlogstatus –av
 Output of ‘jlogdup –V INPUT set=<problematic logset OUTPUT set=null>’
 jdiag –dvL

Index related issues


 Output of ‘list-index –a <filename>’ from jshell
 Output of ‘verify-index –rav <filename>’ from jshell
 Output of JQL appended with the NOINDEX clause.
 jdiag –dvL

Trigger related issues


 Output of ‘list-trigger –a <file name>’
 A copy of the trigger routine
 jdiag -dvL

Distributed file issues


 Output of ‘list-distrib’ and ‘verify-distrib’ on the distributed file
 Output of echo $JEDIFILEPATH
 Output of echo $JEDI_DISTRIB_FASTSCAN
 Output of jstat and jrf on part files
 A copy of the partition algorithm

JR file issues
 Output of jstat –v <file name>
 jdiag –dvL

jRFS issues
 procedure followed in setting up jRFS
 a copy of ‘CT VOC <some file>’ from both the servers
 ps –ef | grep jRFS from both the servers
 Client and server configuration along with "jdiag -dv" details as separate sets
 Logfiles obtained by switching ON log and trace options in config files under both servers.

96 PACS
Support Handbook

jDP issues
 procedure followed in setting up jDP
 Output of ‘irpcd status’
 Output of ‘ls –la /usr/jbc’
 Output of ‘nav_util check datasource (TDP_name)’
 Output of ‘nav_util execute TDP_name’
 Output of ‘LIST TABLES’ from NavSQL prompt
 OGLOBUS Issues

JUPORT issues
Setup issues
 The contents of ‘juport.ini’ file.
 The ‘.profile’ (Unix) or ‘remote.cmd’ file.
 The commands used and the procedures followed, with screen shots

BROWSER

Information Required for All Issues


 Whether JCA architecture is being used or TCServer is used?
 Version of T24, T24 Browser, TCServer/TOCF, Web Server/App server(Tomcat/Jboss/WebSphere/Weblogic..etc), JSDK
and Internet Explorer
 Does the problem occur in Classic / Desktop?
 Is the problem re- creatable via OFS?
 Whether the problem occurs on any particular Browser release.
 Steps for replicating the problem along with screenshots
 Log files from Browser. Kindly refer to the section “Setting Log level to DEBUG for Browser related issues” for getting these
logs.

Setting Log level to DEBUG for Browser r elated issues

If Temenos Connector is used follow the below steps to give us the TC logs
1. For TCServer log level need to be set as DEBUG as given below

i) Set the log level to DEBUG in the tcslog.properties (which is in …\tcserver\conf\TCServer) file as shown below

log4j.logger.common=DEBUG, file

log4j.logger.tcs=DEBUG, file

log4j.logger.ofs=DEBUG, file

log4j.logger.tcp=DEBUG, file

ii) Set the log level to DEBUG in the tcclient.properties (which is in ... \BrowserWeb\WEB-INF\conf) file as shown below

log4j.logger.common=INFO, file

log4j.logger.channels=INFO, file

log4j.logger.tcc=INFO, file

2. After setting the log level given in step 1, replicate the problem and then send us

i) All the global.log files from the \tcserver\log directory of the TCServer installation

ii) All the global.log files from the \BrowserWeb\WEB-INF\log directory of the Browser installation.

97 PACS
Support Handbook

For TCServer or JCA used, follow the below steps to give us the BrowserServlet logs which is generic for both.

1. For enabling BrowserServlet logs, the log level need to be set to DEBUG in the log4j.properties found in "\BrowserWeb\WEB-
INF\classes\" directory as given below

# file appender, location of the file is application server dependant

################################################################################

log4j.appender.logFile=org.apache.log4j.RollingFileAppender

log4j.appender.logFile.layout=org.apache.log4j.PatternLayout

log4j.appender.logFile.layout.ConversionPattern=%n%d [%t] %-5p %c %x - %m%n

log4j.appender.logFile.File= \jboss423\server\default\deploy\BrowserWeb.war\WEB-
INF\log\browser.log

Note: In the above File attribute of the logFile appender, give the complete path where the browser.log has to be written.

log4j.appender.logFile.MaxFileSize=512KB

log4j.appender.logFile.MaxBackupIndex=999

# default logging in Browser

################################################################################

# default logging is to the console, for output to the file, comment following line and uncomment the subsequent line

#log4j.logger.com.temenos=ERROR, console

log4j.logger.com.temenos=DEBUG, logFile

# default logging for beans and other classes in the t24browser package and its subpackages

################################################################################

log4j.logger.com.temenos.t24browser=DEBUG

# default logging for servlets and servlet filters

################################################################################

log4j.logger.com.temenos.t24browser.servlets=DEBUG

2. After setting the BrowserServlet log level as given in step 1, replicate the problem and then send us all the log files from the File
attribute of the logFile appender (for e.g in this case the browser.log files from it is the
\jboss423\server\default\deploy\BrowserWeb.war\WEB-INF\log directory)

NOFILE ENQUIRY
 SS of the corresponding ENQUIRY.
 Nofile routines attached ( if local)

OFS Related Issues


Information required when opening a OF issue
 Method of process used, such as

• OFS.POST.MESSAGE

• OFS.CONNECTION.MANAGER,

• tSS

• OFS.GLOBUS.MANAGER or PHANTOM process

 Error recorded in any of the OFSLOG files if any


 Application and sample OFS string used to process
 Relevant OFS.SOURCE, EB.PHANTOM records if any

98 PACS
Support Handbook

 Any local routine involved to create the OFS messages


 Corresponding OFS.REQUEST.DETAIL record.

To enable the OFS.REQUEST.DETAIL please set the MAINT.MSG.DET field to Y and give some prefix in the field DET.PREFIX in
OFS.SOURCE record.

 Full view of the OFS.SOURCE being used.

Problem in printing Deal slip / Enquiry report/ HOLD.CONTROL/


EB.TABLE.DEFINITION
For deal slips
 DEAL.SLIP.FORMAT record
 VERSION record
 REPORT.CONTROL record
 DE.FORM.TYPE record
 PRINTER.ID record
 PRINTER.ATTRIBUTES record
 jsh-->SP-STATUS
 Server printing or local printing.
 &HOLD& record
 HOLD.CONTROL record
 USER record who is printing the deal slip.

For enquiry reports


 ENQUIRY record.
 ENQUIRY.REPORT record
 REPORT.CONTROL record
 DE.FORM.TYPE record
 PRINTER.ID record
 PRINTER.ATTRIBUTES

The output of &HOLD& from jBASE prompt

SP-STATUS output from jBASE prompt

Run Time Errors


1. T24 Desktop front end details
2. jshow -c GET.STANDARD.SELECTION.DETS
3. jshow -c S.READ.FILE
4. whether the problem occurs in all core/local application or only particular core/local application and also let us know whether
problem occurs during I or A or E or L mode.
5. Does Re-installing the current DT build resolves the reported problem?. Also let us whether the reported problem occurs in
latest T24 Desktop build.

SEAT
Basic information required for SEAT related problem
 OFS.SOURCE record
 OFS.REQUEST.DETAIL

99 PACS
Support Handbook

 Processed/Error data from the SEAT.OUT directory and from the SEAT.RESULTS.
 Global.log file from the tcserver used
 For all the problems related to the uploading and processing
 Full view of the uploading script record from SEAT.SCRIPTS, if it has sequencing concept then all the sequenced records are
required.
 Full view of the tcserver.xml from the tcserver/conf/TCServer directory.
 Full view of the OFS.REQUEST.DETAIL and the output result from the processed directory (SEAT.OUT)
 For the problems related to the failure in updation to the SEAT.SCRIPT.RESULT.FILES and SEAT.SCRIPT.FIELD.VALUES
 Full view of the SEAT.APPLICATION.MANAGER for the corresponding application
 Full view of the SEAT.SCRIPT.RESULT.FILES
 Full view of the SEAT.SCRIPT.FIELD.VALUES
 Full view of the OFS.REQUEST.DETAIL and the output result from the processed directory (SEAT.OUT)

For the problems related to the failure in triggering the TEST seat routines
 Full view of the SEAT.APPLICATION.MANAGER for the corresponding application
 Full view of the SEAT.EVENT.MANAGER given in the SEAT.APPLICATION.MANAGER
 The test routines specified in the SEAT.EVENT.MANAGER
 Full view of the OFS.REQUEST.DETAIL and the output result from the processed directory (SEAT.OUT)

SMS
 USER.SMS.GROUP & USER Records;
 Screenshots & instance of the problem;

SMS problems
 Provide records from the following files:
 USER profile.
 USER.SMS.GROUP record.
 SMS restriction required and what is achieved?
 Screenshots explaining the problem in detail
 If the problem occurs across all applications or is it specific to one application.
 Jshow of the following routines SMS.VERIFY,CONTROL.USER.PROFILE, ENQ.SMS.VERFIY
 COMPANY record
 Corresponding VERSION or ENQUIRY record used
 Problematic record/contract which is displayed in enquiry or shouldn't have displayed in

Enquiry/accessed

For problems related to SPF corruption - TAFC Compliance


 Full view of SPF record
 Screen shot of the actual error message while logging to the system
 Reason behind corruption like editing SPF / UTF8 conversion/any other reason
 CT F.SPF ‘SYSTEM’ (from jshell level)
 CT F.SPF.CHECK ‘SYSTEM’ (from jshell level)
 jshow –c SPF (from jshell level)
 jshow –c CHECK.SPF (from jshell level)

100 PACS
Support Handbook

 jsh-->CT VOC F.SPF


 jsh-->jstat -v F.SPF
 profile and jdiag records

For problems related to SPF corruption - TAFJ Compliance


 Full view of SPF record
 TAFJ release and database used.
 If it’s Oracle, check the F.SPF.CHECK>SYSTEM and see how many lines it has. (Must be more than 9 lines, if it is one line,
then F.SPF.CHECK file is corrupt)
 If F.SPF.CHECK>SYSTEM is one line, then please reach 24by@temenos.com immediately.
 Please check the NLS_CHARACTERSET used at database level. If character set is other than AL32UTF8, then please reach
24by@temenos.com immediately with below details.
 select * from v$nls_parameters where parameter='NLS_CHARACTERSET'
 select * from v$nls_parameters where parameter in ('NLS_CHARACTERSET');
 After restoring the database and ensure we have minimum 9 lines in F.SPF.CHECK>SYSTEM, , Set the
NLS_CHARACTERSET as AL32UTF8.
 After confirming the results, please get the new code from LN team and issue the code.
 >tShow SPF
 >tShow CHECK.SPF
 >DBTools –s JQL DESCRIBE F_SPF
 >tDiag

System Tables - TAFC Compliance


Problem with CONDITION.PRIORITY
Provide screen dumps of the following records

CONDITION.PRIORITY record

Prints of the error message while amending the CONDITION.PRIORITY record.

Problem with wrong group calculation:


The full view of related XX.GEN.CONDITION record

From jBASE

----àCT FXXX.XX.GEN.COND.PRTY where XXX is the company mnemonic and XX is the related application id

PICKING UP WRONG TAX FOR A CUSTOMER


Full view of related XX.GEN.CONDITION record

From jBASE

>LIST FXXX.TAX.GEN.CONDITION

>LIST FXXX.TAX.TYPE.CONDITION

>LIST FXXX.TAX.GEN.COND.PRTY

>LIST FXXX.CONDITION.PRIORITY WITH @ID LIKE TAX...

Replace XXX with respective mnemonic of the company.

Problem with TAX not calculated or wrongly calculated


Full view corresponding CUSTOMER & CUSTOMER.CHARGE

101 PACS
Support Handbook

Full view of corresponding ACCOUNT or CONTRACT

Full view of associated XX.GEN.CONDITION

Full view of APPL.GEN.CONDITION if present for the related application

Full view of TAX, TAX.TYPE

Full view of associated TAX.TYPE.CONDITION, TAX.GEN.CONDITION.

CUSTOMER.POSITION related problems:


Results of the enquiry record CUSTOMER.POSITION and CUSTOMER.POSITION.SUMMARY

1) Full view of the CUSTOMER.POSITION and CUSTOMER.POSITION.SUMMARY Enquiry record

2) Full view of the Problematic CUSTOMER

3) Output from jshell prompt

a) SELECT FXXX.LIMIT WITH @ID LIKE ...<<CUS.ID>>...

> LIST FXXX.LIMIT

b) SELECT FXXX.LIMIT$HIS WITH @ID LIKE ...<<CUS.ID>>...

> LIST FXXX.LIMIT$HIS

c) SELECT FXXX.LIMIT.TXNS WITH @ID LIKE ...<<CUS.ID>>...

> LIST.ITEM FXXX.LIMIT.TXNS

d) Run CUSTOMER.POSITION enquiry and run below command

>LIST FXXX.CUSTOMER.POSITION WITH @ID LIKE ...<<CUS.ID>>... ONLY

Replace XXX with company mnemonic & <<CUS.ID>> with problematic Customer.

System Tables - TAFJ Compliance


Problem with CONDITION.PRIORITY
Provide screen dumps of the following records

CONDITION.PRIORITY record

Prints of the error message while amending the CONDITION.PRIORITY record.

Problem with wrong group calculation:


The full view of related XX.GEN.CONDITION record

From jBASE

----àCT FXXX.XX.GEN.COND.PRTY where XXX is the company mnemonic and XX is the related application id

PICKING UP WRONG TAX FOR A CUSTOMER


Full view of related XX.GEN.CONDITION record

From DBTools

>LIST-ITEM FXXX.TAX.GEN.CONDITION

>LIST-ITEM FXXX.TAX.TYPE.CONDITION

>LIST-ITEM FXXX.TAX.GEN.COND.PRTY

>LIST-ITEM FXXX.CONDITION.PRIORITY WITH @ID LIKE TAX...

Replace XXX with respective mnemonic of the company.

102 PACS
Support Handbook

Problem with TAX not calculated or wrongly calculated


Full view corresponding CUSTOMER & CUSTOMER.CHARGE

Full view of corresponding ACCOUNT or CONTRACT

Full view of associated XX.GEN.CONDITION

Full view of APPL.GEN.CONDITION if present for the related application

Full view of TAX, TAX.TYPE

Full view of associated TAX.TYPE.CONDITION, TAX.GEN.CONDITION.

CUSTOMER.POSITION related problems:


Results of the enquiry record CUSTOMER.POSITION and CUSTOMER.POSITION.SUMMARY

1) Full view of the CUSTOMER.POSITION and CUSTOMER.POSITION.SUMMARY Enquiry record

2) Full view of the Problematic CUSTOMER

3) Output from jshell prompt

a) > LIST FXXX.LIMIT WITH @ID LIKE ...<<CUS.ID>>...

b) > LIST FXXX.LIMIT$HIS WITH @ID LIKE ...<<CUS.ID>>...

c) > LIST.ITEM FXXX.LIMIT.TXNS WITH @ID LIKE ...<<CUS.ID>>...

d) Run CUSTOMER.POSITION enquiry and run below command

>LIST-ITEM FXXX.CUSTOMER.POSITION WITH @ID LIKE ...<<CUS.ID>>... ONLY

Replace XXX with company mnemonic & <<CUS.ID>> with problematic Customer.

TEMENOS CONNECTORS - TAFC Compliance


Information required for all problems
 TCServer release with patch details
 Java version
 Configuration files tcserver.xml & environment.vars files from the \tcserver\conf directory
 LOG files from the \tcserver\log directory with the log level set to DEBUG for the tcs, ofs components and for ofsml,
filelistener, batchfilelistener...etc if the problem is specific to those components
 For e.g. for OFSML related problems the ofsml component need to be set with DEBUG level as given below
 log4j.logger.ofsml=INFO, file
 For batchfilelistener related problems batchfilelistener component need to be set with DEBUG level as given below
 log4j.logger.batchfilelistener=DEBUG, file
 If the problem happens in both Classic and Desktop using OFS.

In case of using TOCF(EE)


a) If jboss used as a web application server

 t24-ds.xml
 t24-destinations-service.xml
 tocfee.ear pack
 List of files under the <Jboss_home>/server/default/deploy directory.
 server.log (which is under the directory of <Jboss_home>/default/log )
 Send the version of java by typing the below command in jshell prompt
 Jsh -->java –version

103 PACS
Support Handbook

b) If websphere used as a web application server.

 tocfee.ear pack
 In R10 and higher releases ,Admin console screenshot from the path "Resource adapters > > TOCF T24 Resource Adapters
> J2C connection factories > T24 JCA Connection Factory > Custom properties".

(or)

In R09 release Admin console from the path "Resource adapters > jRemote > J2C connection factories > T24 JCA Connection Factory
> Custom properties".

System.out and System.err log files from the directory (/WebSphere/profiles/AppSrv01/logs/server1 )

Send the version of java by typing the below command in jshell prompt

Jsh -->java –version

c) If Weblogic used as a web application server.

 tocfee.ear pack
 In R10 and higher releases , Admin console screenshot from the path ""Deployments > tocfT24ra-ra > Configuration >
Outbound Connection Pools > JConnectionFactory > Properties".

(or)

 In R09 release Admin console from the path “Deployments > jremote-ra > Configuration > Outbound Connection Pools >
JConnectionFactory > Properties”.
 AdminServer.log files from the directory
 (/WebLogic/user/projects/domains/base_domain/servers/AdminServer/logs)
 Send the version of java by typing the below command in jshell prompt
 Jsh -->java –version

For MQ related problems:


IBM Websphere MQ release version.

Information required for all problems


 TCServer release with patch details
 Java version
 Configuration files tcserver.xml & environment.vars files from the \tcserver\conf directory
 LOG files from the \tcserver\log directory with the log level set to DEBUG for the tcs, ofs components and for ofsml,
filelistener, batchfilelistener...etc if the problem is specific to those components
 For e.g. for OFSML related problems the ofsml component need to be set with DEBUG level as given below
 log4j.logger.ofsml=INFO, file
 & for batchfilelistener related problems batchfilelistener component need to be set with DEBUG level as given below
 log4j.logger.batchfilelistener=DEBUG, file
 If the problem happens in both Classic and Desktop using OFS.

For Temenos Connectors, following additions are required, in case client is using
TOCF(EE)
 t24-ds.xml
 t24-destinations-service.xml
 tocfee.ear pack
 List of files under the <Jboss_home>/server/default/deploy directory.
 server.log (which is under the directory of <Jboss_home>/default/log )
 Send the version of java by typing the below command in jshell prompt

104 PACS
Support Handbook

 Jsh -->java -version

For MQ related problems:


1. IBM Websphere MQ release version.

TEMENOS CONNECTORS - TAFJ Compliance


Information required for all problems
 Java version
 For e.g. for OFSML related problems the ofsml component need to be set with DEBUG level as given below
 log4j.logger.ofsml=DEBUG, file
 For batchfilelistener related problems batchfilelistener component need to be set with DEBUG level as given below
 log4j.logger.batchfilelistener=DEBUG, file
 If the problem happens in both Classic using OFS.

In case of using TOCF(EE)


a) If jboss used as a web application server

 tocfee.ear pack
 tafj-services.xml
 List of files under the <Jboss_home>/server/default/deploy directory.
 server.log (which is under the directory of <Jboss_home>/default/log )
 Send the version of java by typing the below command in jshell prompt
 Jsh -->java –version

b) If websphere used as a web application server.

 tocfee.ear pack.
 System.out and System.err log files from the directory (/WebSphere/profiles/AppSrv01/logs/server1 )
 Send the version of java by typing the below command in jshell prompt
 Jsh -->java –version

c) If Weblogic used as a web application server.

 tocfee.ear pack
 AdminServer.log files from the directory
 (/WebLogic/user/projects/domains/base_domain/servers/AdminServer/logs)
 Send the version of java by typing the below command in jshell prompt
 Jsh -->java –version

d) TAFJ LOGS

Set the log level to DEBUG in the TAFJTrace.properties present under the 'conf' directory of TAFJ home directory.

Change INFO to DEBUG in the following lines in TAFJTrace.properties

log4j.logger.T24=DEBUG, t24

log4j.logger.DATABASE=DEBUG, database

log4j.logger.RUNTIME=DEBUG, runtime

log4j.logger.MDB=DEBUG, mdb

log4j.logger.EJB=DEBUG, ejb

105 PACS
Support Handbook

after making the above changes in TAFJTrace.properties, kindly clear all the log files in 'log' and 'log_T24' directory and restart the
Web Application Server (i.e. jBoss, Websphere, Weblogic).

b. Recreate the problem and send us the following files in sync for analysis.

a) Once the problem replicates, send us all the T24.log files from …\<TAFJ_HOME>\log_T24 directory.

b) All the database.log, runtime.log, mdb.log, ejb.log files from …\<TAFJ_HOME>\log directory.

For MQ related problems:


IBM Websphere MQ release version.

Information required for all problems


 Java version
 Configuration files tcserver.xml
 If the problem happens in both Classic using OFS.

106 PACS
Support Handbook

T-VERIFY
Problem in capturing transactions through Phantoms and Services.
1. Full view of TV.PARAMETER record
2. Full view of OFS.SOURCE record, List of IN.QUEUE.DIR and OUT.QUEUE.DIR directories.
3. Full view of EB.PHANTOM record
4. Full view of TV.INTERFACE record
5. List of records from F.TV.LINKED.IDS
6. Record in TRANS.LOG - CT VOC <<TRANS.LOGid>>
7. jshow output for TV.TRANS.STORE.PROCESS, TV.PROCESS.LINKED.REFERENCE

Problem with Unnecessary Tracers while capturing transactions


1. Full view of TV.PARAMETER record
2. CT F.LOCKING TRANS.TRACE

Problem in Replay
1. Full view of tcserver.xml (in order to check whether BatchFileListener is set)

Version
 VERSION record.
 Deal under VERSION screen showing error.
 Deal using main full screen.
 Whether the version is created using Version Designer?
 Problematic transaction in SEE mode.
 VERSION.CONTROL record corresponding to the application or version
 VERSION.CONTROL record SYSTEM ( if exists)
 Routines missing( SUBROUTINE_CALL_FAIL) errors àjshow of the routines from jshell prompt.
 Local routines attached in versions

107 PACS
Support Handbook

T24 Administration
Activate Passwords
Before the TEMENOS staff is expected or due to access your system:

 Set the passwords for Unix logins.


 Activate T24 USER profiles by using History restore.
 Change the password using PASSWORD.RESET.
 `If supervision is required, ensure your staffs are available.

When TEMENOS staff arrives or connect:

 Advise them of login names, passwords and system availability.


 Network logon procedures.
 Printers available for use.
 Any unique site instructions.

If a TEMENOS consultant is on-site, they will require use of a PC, printer and telephone.

Archive Related Issues


 ARCHIVE record
 ARC.GENERIC.REQUEST record
 Screenshot of the error generated while running the archive service
 COMO of the archive service

Licensing Issue
For Maintenance Code Request
 Full view of SPF record
 Date until which we need to issue the Maintenance code.

For New Product Code Request


 Full view of SPF record
 T24 Product for which you need the code.

For additional T24 user license


 Full view of SPF record
 Details of the additional number of license required.

For all problems which inputting the Maintenance code


 Full view of the current SPF where the code is being entered.
 Details of the code supplied by Temenos
 Current server date (not the T24/Globus Bank date)

Multi APP Server Architecture <Setup Queries>


Setup Issues:
 Oracle client information from the application

108 PACS
Support Handbook

 Oracle database version from the database server


 Oracle tnsping <host> from application server Vs Database server and vice versa.

Locking issues on Multi application server


 Output of jDLS -dvL <From all application servers>
 NFS or File mounting details

Multi-language problems - TAFC Compliance


1. .profile/remote.cmd
2. jdiag
3. Snapshot of the error message
4. ASCII.VAL.TABLE and ASCII.VALUES records setup
5. Front end version being used(for Desktop/Browser)
6. If Desktop,

• Font and Font Script used

• Socket connection enabled or not

If Browser,
If TCServer,

a. browserParameters.xml file in \webapps\BrowserWeb directory


b. browserConnection.xml file in \webapps\BrowserWeb\WEB-INF\conf directory
c. global.log
d. environment.vars

If JBOSS,

a. t24-ds.xml file
b. browser.log

Multi-language problems - TAFJ Compliance


1. .profile/remote.cmd

2. Jdiag

3. Snapshot of the error message

4. ASCII.VAL.TABLE and ASCII.VALUES records setup

5. If Browser,

If Browser,
If TCServer,

a. browserParameters.xml file in \webapps\BrowserWeb directory


b. browserConnection.xml file in \webapps\BrowserWeb\WEB-INF\conf directory
c. global.log
d. environment.vars

If JBOSS,

a. t24-ds.xml file
b. browser.log

109 PACS
Support Handbook

Performance Issues
During ONLINE - TAFC Compliance
 Screenshots with the hanging DT/browser
 The following from jBASE prompt:
 >SHOW-ITEM-LOCKS
 >WHERE (V
 $ mw42 -f -e 1 300>mw42.out --
mw42 for 5 mins in the record mw42.out. FTP this record from bnk.run directory
 If External database, XMLdriver.log

During ONLINE - TAFJ Compliance


 Screenshots with the hanging DT/browser
 The following from TAFJ classic session .
 To know the locks - > DBTools –s JQL LOCK
 To get the mw42 kind of output, URL syntax: <<host>>:<<http_port>>/ SessionMonitor/
 If External database, XMLdriver.log

During COB
 COMO of all the agents at the time of hanging
 >WHERE (V
 >SHOW-ITEM-LOCKS
 >mw42
 >LIST F.TSA.STATUS
 $ps –ef | grep tSA

Performance issue with COB jobs - TAFC Compliance


 JOB.TIMES for the problematic job.
 Download JOB TIMES analyser and REPORT TIMES analyser tool from portal and send us the .csv files generated

Performance issue with COB jobs - TAFJ Compliance


 JOB.TIMES for the problematic job.
 Download JOB TIMES analyser and REPORT TIMES analyser tool from portal and send us the .csv files generated
 To check Servlet Navigation - URL Syntax: <<host>> :<< port>>/TAFJEE/
 To know the locks - > DBTools –s JQL LOCKS
 To get the mw42 kind of output, URL syntax: <<host>>:<<http_port>>/ SessionMonitor/

Printer Issues - TAFC Compliance


 Whether the Print problem is with Server print or Local Print
 Whether the Print problem occurs only on enquiries or versions or any specific application
 Full view of USER record and any attached USER.SMS record
 Corresponding PRINTER.ID, DE.FORM.TYPE, REPORT.CONTROL, ENQUIRY.REPORT,
 VERSION,DEAL.SLIP.FORMAT records
 BROWSER.PREFERRENCES record for the USER
 Screenshots of the error messages if any;

110 PACS
Support Handbook

 jsh-->SP-STATUS
 jsh-->cd $JBCSPOOLERDIR
 jsh-->jstat -v jspool_log
 jsh-->jdiag

Printer Issues - TAFJ Compliance


 Whether the Print problem is with Server print or Local Print
 Whether the Print problem occurs only on enquiries or versions or any specific application
 Full view of USER record and any attached USER.SMS record
 Corresponding PRINTER.ID, DE.FORM.TYPE, REPORT.CONTROL, ENQUIRY.REPORT,
 VERSION,DEAL.SLIP.FORMAT records
 BROWSER.PREFERRENCES record for the USER
 Screenshots of the error messages if any;
 >tDiag
 &HOLD& - Generated in the path mentioned in the variable temn.tafj.printer.directory.hold in tafj.properties

Processing Maintenance Code Requests


Maintenance Code
Maintenance codes enable TEMENOS to monitor the licensing and usage of T24. A maintenance code is linked to the date on which
maintenance fees are due. On receipt of the appropriate maintenance fees from a client, a maintenance code will be generated when
requested and distributed by the Licensing team to allow users to continue processing on T24.

Generate and Provide New Maintenance Code


All maintenance code requests must be logged on CSS, similar to other support requests. In order for maintenance codes to be
processed, the clients SPF record must be available. If this is not originally provided, the l Licensing team will request the same. We
recommend you to provide the SPF when logging a maintenance code request.

Rejection of Maintenance Code Request


If a client requests a maintenance code but has not paid maintenance fees, the request will be rejected until the appropriate fees are
paid. The client will be informed of the reason for this.

Product Installation Issues - TAFC Compliance


 COMO records related to XXX/T24.UPGRADE service
 BATCH record XXX/T24.UPGRADE
 SPF,COMPANY records
 Problematic records in SEE mode - if the problem is related to authorisation of the record.
 Jsh-->CT F.LOCKING MB.CLIENT
 jsh -->COUNT F.COMPANY WITH APPLICATIONS EQ 'XX'
 where XX is the product installed.
 jsh -->jshow -c CHECK.APPLICATION

Product Installation Issues - TAFJ Compliance


 COMO records related to XXX/T24.UPGRADE service
 BATCH record XXX/T24.UPGRADE
 SPF,COMPANY records
 Problematic records in SEE mode - if the problem is related to authorization of the record.

111 PACS
Support Handbook

 DBTools -s JQL LIST-ITEM F.LOCKING MB.CLIENT


 tShow CHECK.APPLICATION

STMT ENTRY ARCHIVE


 Full view of ARCHIVE S STATEMENT
 jstat -v FXXX.STMT.ENTRY
 jrf -Rv FXXX.STMT.ENTRY
 COUNT FXXX.AC.STMT.HANDOFF WITH TO.DATE LT purge.date
 COUNT FXXX.STMT.ENTRY WITH BOOKING.DATE LE purge.date AND WITH @ID UNLIKE F...
 COUNT FXXX.STMT.ENTRY$ARC
 Full view of ACCOUNT.STATEMENT, ACCT.STMT.PRINT for few sample accounts for which entries are not purged

Replace XXX with respective mnemonic of the company and purge.date with the archive PURGE.DATE

Updates - TAFC Compliance


Updates hanging problem:
 Full output of executing updater command from jshell prompt.
 COMO corresponding to updates service
 Full view of SPF record
 jsh-->jdiag -c
 jsh-->jshow -c java
 jsh-->echo $PATH
 jsh-->T24Version
 jsh-->.profile(or remote.cmd in case operation system is Windows)

Dependency Errors:
 Full output of the executing of updater from jsh prompt.
 Full view of SPF record
 SysDef.xml file used to download the updates
 jsh-->T24Version
Note: the above command is case-sensitive

"Unable to open & file" error:


 jsh-->pwd
 jsh-->CT SYSTEM TEMP.RELEASE
 copy the path shown in the above command
 jsh-->ls -ltr <<above copied path>>
 jsh-->CT VOC SYSTEM
 jsh-->jstat -v SYSTEM
 jsh-->.profile(or remote.cmd in case operation system is Windows)

"Unable to open <<UPDATE NAM E>>" error:


Output of the below command from jsh prompt

 jsh-->tar
 jsh-->gtar

112 PACS
Support Handbook

 COMO corresponding to updates service


 Untar the problematic tar file and check whether the file is not corrupted and let us know the result

SUBROUTINE_CALL_FAIL error after installing updates:


COMO corresponding to updates service

jsh-->jshow -c <<problematic routine>>

 For example:
 If the subroutine is OVERLAY.EX,
 The below command will fetch the component name
 jsh-->CT F.PGM.DATA.CONTROL BP>OVERLAY.EX
 BP>OVERLAY.EX

001 EB

002

003

004 S

005 EB_API

Now send us the output of the below command

 jsh-->ls -ltr t24lib/eb_api


 jsh-->ls -ltr t24bin/eb_api

After running BNK/T24.UPDATES service, SPF not updated or data records pertaining to that update not released:

COMO corresponding to updates service

BATCH record BNK/T24.UPDATES

CT SYSTEM TEMP.RELEASE

jsh-->COUNT %F.SL

jsh-->echo $JEDIENABLEQ2Q

jsh-->echo $JEDIFILENAME_SYSTEM

jsh-->jstat -v SYSTEM

Updates - TAFJ Compliance


Updates hanging problem:
 Full output of executing updater command from Classic session.
 COMO corresponding to updates service and the ID will be like UPD.RXX.UPDATE_NAME
 Full view of SPF record
 >tDiag
 >tRun T24Version
 Full view of TAFJ.properties and default.properties file.

Upgrade Issues - TAFC Compliance


 COMO records related to T24.UPGRADE service
 BATCH record XXX/T24.UPGRADE where XXX- Company Mnemonic
 The following records from &SAVEDLISTS&

113 PACS
Support Handbook

• REL.XXXXX.FILES

• REL.XXXXX.DATA

• REL.XXXXX.PGM.FILE

 LIST F.SPF
 LIST F.COMPANY
 CT SYSTEM TEMP.RELEASE
 If any specific data record is not released, then the following record:
 CT F.PGM.DATA.CONTROL ‘F.XXX>YYY’

WHERE XXX à File.name and YYYàRecord id

Eg. COB.INITIALISE BATCH record missing

CT F.PGM.DATA.CONTROL ‘F.BATCH>COB.INITIALISE’

 CT F.RELEASE.DATA ‘F.XXX>YYY’
 CT VOC MB.CLIENT

Upgrade Issues - TAFJ Compliance


 COMO records related to T24.UPGRADE service
 BATCH record XXX/T24.UPGRADE where XXX- Company Mnemonic
 The following records from &SAVEDLISTS&
 REL.XXXXX.FILES
 REL.XXXXX.DATA
 REL.XXXXX.PGM.FILE
 >DBTools –s JQL LIST-ITEM F.SPF
 >DBTools –s JQL LIST-ITEM F.COMPANY
 If any specific data record is not released, then the following record:

114 PACS
Support Handbook

T24 Upgrade and Conversation


CONVERSION Issues - TAFC Compliance
 COMO records related to RUN.CONVERSION service
 Problematic CONVERSION.DETAILS record
 Problematic data record which is not converted properly
 The corresponding record from F.PGM.DATA.CONTROL and F.RELEASE.DATA

CT F.PGM.DATA.CONTROL ‘F.XXX>YYY’

CT F.RELEASE.DATA ‘F.XXX>YYY’

where XXX- denotes FILE NAME and YYY denotes record ID

i.e. CT F.PGM.DATA.CONTROL 'F.ENQUIRY>CURRENCY-LIST'

CONVERSION Issues - TAFJ Compliance


• COMO records related to RUN.CONVERSION service

• Problematic CONVERSION.DETAILS record

• Problematic data record which is not converted properly

• The corresponding record from F.PGM.DATA.CONTROL and F.RELEASE.DATA

DBTools –s JQL LIST-ITEM F.PGM.DATA.CONTROL F.XXX>YYY

DBTools –s JQL LIST-ITEM F.RELEASE.DATA ‘F.XXX>YYY’

where XXX- denotes FILE NAME and YYY denotes record ID

i.e. DBTools –s JQL LIST-ITEM F.PGM.DATA.CONTROL F.ENQUIRY>CURRENCY-LIST

Conversion related Problem <Jbase to Oracle using RDMB


Conversion>
 Provide us the copy of the ./rdbmsConversion directory from bnk.run
 Details of Migration procedure from Distribution/TAM

TCIB & TCMB


TCIB – Temenos Connect Internet Banking:
1. T24 Release - (example – R13, R15, etc.)

2. TCIB build details – (TCIB_RETAIL_R15.06)

3. TAFJ or TAFC –

4. Full view of SPF record from the problematic environment -

5. Application server used along with Version number - (JBoss 5, WebSphere 7.1, etc..)

6. Whether the reported problem is from Deployer or developer version?

7. Edge Connect IDE details – (edgeConnect5_4_1__5)

8. Steps to replicate (if applicable)– (1. Login TCIB application, 2.Click Move money, 3. Transaction failed displaying “XYZ”)

9. Screenshots for the reported problem (if applicable)-

10. Application Server logs (if applicable)

115 PACS
Support Handbook

TCMB – Temenos Connect Mobile Banking


1. T24 Release - (example – R13, R15, etc.)

2. TCMB build details -

3. TAFJ or TAFC –

4. Full view of SPF record from the problematic environment -

5. Application server used along with version number -

6. Whether the reported problem is from Deployer or developer version?

7. Edge Connect IDE details – (edgeConnect5_4_1__5)

8. Steps to replicate (if applicable) – (1. Login TCMB application, 2.Perform Fund transfer, 3. Transaction failed displaying
“XYZ”)

9. Whether reported issue happens in all platforms like IPhone, Android and Windows? If no, specify which platform.

10. Screenshots for the reported problem (if applicable)-

11. Application Server logs (if applicable)

Teller
Teller
Teller transaction problem
 TELLER RECORD
 TELLER.TRANSACTION involved in the Teller
 TELLER.PARAMETER
 ENTRIES GENERATED FOR THE SAME (STMT AND CATEG ENTRIES)
 Output of enquiry TXN.ENTRY.MB for the problematic Teller transaction
 Full view of ACCOUNTs involved in the teller transaction
 Full view of TELLER.ID (of the user who posted the transaction) in INPUT mode and SEE mode.
 Full view of TT.STOCK.CONTROL of the Teller internal account
 Physical cash in hand with the Teller user.

Passbook printing proble m


 TELLER.PASSBOOK
 TELLER.PBOOK.PRINTED of the passbook account
 Electronically scanned Output of the passbook
 Full view of passbook ACCOUNT
 ACCOUNT.STATEMENT
 STMT.PRINTED
 ACCT.STMT.PRINT

TELLER FINANCIAL SERVICES


For all TFS related problems, provide us
 Full view of problematic TELLER.FINANCIAL.SERVICES transaction record
 Full view of child transactions generated for the TELLER.FINANCIAL.SERVICES transaction.

116 PACS
Support Handbook

 Full view of TFS.TRANSACTION used in the problematic TELLER.FINANCIAL.SERVICES transaction.


 Full view of TFS.PARAMETER record.
 Execute the below command from database prompt and provide the output.

117 PACS
Support Handbook

Trade Finance
LETTERS.OF.CREDIT

LC Delivery Problem (Problem with advices)


Provide screen dumps of the following records

 LETTER.OF.CREDIT record
 DRAWINGS records.
 LC.PARAMETERS record.
 EB.ADVICES record. ID can be obtained from the ACTIVITY CODE field of the transaction.
 DE.O.HEADER record of the delivery message if the message has been generated and a delivery reference key is present in
the transaction.
 DE.MESSAGE, DE.MAPPING and DE.FORMAT.PRINT or DE.FORMAT.SWIFT records.
 Outcome of the DE.O.HANDOFF record using ENQ DE.HANDOFF.DETS OR
 In Database level run SEE.HANDOFF; enter Delivery key as for the DE.O.HEADER, e.g. SEE.HANDOFF
D2005020400005082700
 Screen Shot of the message using DE.MM.PRINT.MSG, if the message is formatted.

Online problem with LC or DRAWINGS transaction.


 Examples: Unable to commit the transaction because of an error. The transaction has fields, which have not been updated
correctly.
 If the problem is with a LC transaction, prints the LC transaction and its history record.
 If the problem is with a drawings transaction, then the full view of the DRAWINGS transaction and its history records and
the full view of the live LC transaction
 If the problem is suspected due to combination of several drawings, then the full view of the LC record and in addition the
full view of all the underlying DRAWINGS transaction.

Online FAT AL.ERROR on LIMIT related (either while input, amend, r eversal)
jsh>SEARCH Fxxx.LIMIT.TXNS

String :<<LC.ID>>

String :

Record Keys : *

N record selected

>CT Fxxx.LIMIT.TXNS

Replace xxx with company mnemonic.

Discounted Drawings Problems


 LC.DISCOUNT.BALANCES
 DR.DISC.AMENDMENTS
 LC.BALANCES(IF APPLICABLE)
 DRAWINGS

LIST FBNK.DRAWINGS$HIS WITH @ID LIKE <<DRAWING_ID>... BY @ID DRAWING.TYPE DRAW.CURRENCY


DOCUMENT.AMOUNT VALUE.DATE MATURITY.REVIEW DISCOUNT.RATE DISCOUNT.AMT DATE.LAST.AMORT
DIS.AMORT.TO.DTE DISC.AMT.LOCAL DIS.AMRT.DTE.LCY DOC.AMT.LOCAL DOC.AMT.LC.CCY DOC.AMT.ACC.CCY
PAYMENT.AMOUNT REIMBURSE.AMOUNT DATE.TIME

Balance mismatch in LC
For balance mismatch, supply us with details of STMT.ENTRY, CATEG.ENTRY and RE.CONSOL.SPEC.ENTRY.

118 PACS
Support Handbook

Problem with a particular contract: (following details are needed)

 LC.PARAMETER
 LETTER.OF.CREDIT
 DRAWINGS
 LC.BALANCES(IF APPLICABLE)
 EB.CONTRACT.BALANCES

Problem with Charges


In case the problem deals with charges in LETTER OF CREDIT/DRAWINGS then LC.ACCOUNT.BALANCES has to be provided

LC and Syndicated Lending:


In case of any problem, wherein Syndicated Lending is linked with LC, please provide us

 SL.FACI.BALANCES
 SL.FACI.PART.BALANCE
 SL.ACCOUNT.BALANCES
 SL.FACILITY.LOANS
 SL.FACI.LOAN.CUST.AMT
 SL.TR.LOANS
 SL.FACI.PROD.DETAILS
 LC.BALANCES
 DRAWINGS
 LETTER.OF.CREDIT

119 PACS
Support Handbook

SWAPS
Provide records from the following files:

 SWAP
 SWAP.BALANCES or SWAP.BALANCES.HIST
 SWAP.PARAMETER
 RE.CONTRACT.BALANCES
 SWAP.SCHEDULES

Output of the ENQ SWAP.SCHED.RR for asset and liability.

Output of ENQ SWAP.SCHED.FWD.RR for asset and liability.

If the problem is related to

1) Schedules not processed:

a) History of the problematic deal.

b) SWAP.SCHEDULES

c) Output of the ENQ SWAP.SCHED.RR for asset and liability

d) COMO of BATCH SW.END.OF.DAY for the respective schedule date

e) The HOLIDAY records for the Business centres, local currency and the currencies traded.

2) Limit related issues:

a) LIMIT.TXNS of the respective contract and the LIMIT.PARAMETER

3) Accounting /Mismatch error:

a) The TRANS.JOURNAL (TRANS.JOURNAL2 –Prior to R8 / TXN.JOURNAL.PRINT – From R8) of the respective date.

b) All the accounting entries pertaining to the problematic contract

c) RE.CONSOL.SWAP (for releases lesser than R08) / RE.CONSOL.CONTRACT and EB.CONTRACT.BALANCES (for
releases above R08)

d) Full view of the CONSOLIDATE.ASST.LIAB record

e) RE.STAT.MISMATCH and RE.STAT.BAL.REC reports

f) EB.SYSTEM.SUMMARY and EB.JOURNAL.SUMMARY.

g) SWAP.BALANCES record for

4) For Delivery related issues:

a) DE.MESSAGE, DE.MAPPING, DE.FORMAT.SWIFT of the related message.

b) output of the DE.O.HANDOFF record using ENQ DE.HANDOFF.DETS OR

c) In Database level run SEE.HANDOFF; enter Delivery key as for the DE.O.HEADER, e.g. SEE.HANDOFF
D2005020400005082700

d) The HOLIDAY records for the Business centres, local currency, Customer’s Residence and the currencies traded

e) SWAP.ADVICES and SWAP.ACTIVITY records

f) CURRENCY records

5) SWAP Revaluation related:

a) SWAP

b) SWAP.PARAMETER record to know on which method the revaluation was setup.

c) All the accounting entries for the problematic contract

PROVISION

120 PACS
Support Handbook

Provision amount not calculated as expected

1. Full view of PV.ASSET.DETAIL for the problematic contract/account

2. Full view of PV.CUSTOMER.DETAIL for the relevant customer

3. Full view of EB.CONTRACT.BALANCES for the contract/account

4. Full view of relevant PV.PROFILE, PV.MANAGEMENT and PV.MANAGEMENT.CTRL

5. Full view of SPF

IBAN generation

Problem in generating IBAN number while creating accounts

1. Full view of the ACCOUNT record and screenshot of any error while creating account

2. Full view of relevant IN.IBAN.STRUCTURE record

3. Full view of COMPANY and INTERCO.PARAMETER record

4. Full view of sample other account created successfully

5. Full view of records IBAN and T24.IBAN from ALT.ACCT.PARAMETER

6. Full view of ACCOUNT.PARAMETER

7. Full view of SPF

121 PACS
Support Handbook

EDGE
EDGE
1. Basic Information

1.1 Client environment details

Please provide below information

1. EdgeConnect version no – get the exact version from the client. E.g. 5.2.1__45. Client can obtain it from the Help -> About of
Developer IDE.

2. EdgeConnect java version – This can also be obtain from the Help -> About of Developer IDE.

3. EdgeConnect java home – It is available in the Help -> About of Developer IDE.

4. Client’s machine java home – This is the JAVA_HOME of the system where edge is running. It can be different from the edge’s
JAVA_HOME.

5. Client’s machine java version – Best way to obtain this is to run the ‘java –version’ command in the hosted machine’s command
prompt.

1.2 Issue details

In addition to the details provided about the issue, also provide us with

1. Log files – Provide all the log files namely debug.log, Syserr.log, Sysout.log and Security.log. There might be more than one log files
generated appended with TIMESTAMP for each of the above named files. So obtain all concerned archived log files.

2. Project file – In order to recreate the issue , please provide access to remote machine or edge project file (.ifp).

3. Screenshots of the issue which clearly demonstrates the problem. If the issue is occurring on particular event like on click of button,
during phase navigation etcetera then screenshots should include the state before and after the event.

4. For WS issues – WSDL used should be provided along with the screenshot of the web service integration settings.

5. For IDE issues – Provide all the IDE related log files namely :

i. AdministratorSysErr.txt

ii. AdministratorSysOut.txt

iii. DeployerSysErr.txt

iv. DeployerSysOut.txt

v. DeveloperSysErr.txt

vi. DeveloperSysOut.txt

Note – Above log files will be under IDE folder.

6. For license issues – Installkey.txt file needs to be obtain from the client’s edge installed directory under the IDE folder. License will
be provided by the license team.

122 PACS
Support Handbook

AML
ANTI MONEY LAUNDRY
Payments
1. Basic Information

ANTI MONEY LAUNDRY (AML):

2. Client environment details

AML Screening error:

1. Full view of the corresponding VERSION used to create the FUNDS.TRANSFER

2. Jshow of INPUT.ROUTINE and BEFORE.AUTH.ROUTINE being used in the VERSION.

3. Full view of DISPO.ITEMS created.

4. SPF record.

Error while sending the message to AML server:

1. Environment variables

2. .profile record

3. t24-ds.xml

4. XXX/INTEGRATION.SERVICE

5. IF.EVENTS.INTERFACE.TABLES

6. IF.EXIT.POINTS

7. IF.INTEGRATION.FLOW.CATALOG

Error while sending the message to AML server (TAFJ):

1. Full view of IF.EVENTS.INTERFACE.TABLE created for the CUSTOMER record

2. On running the service XXX/INTEGRATION.SERVICE,

• Under TAFJ/log directory – mdb, database, runtime, ejb

• Under TAFJ/log_T24 directory – T24

• COMO of the service XXX/INTEGRATION.SERVICE

123 PACS