Académique Documents
Professionnel Documents
Culture Documents
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.
Support Handbook
Remote 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.
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:
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:
Contact Detail
Contact with any Front Office PACS can be made as follows:
Nungambakkam Perungudi,
Gtalk cshd.helpdesk@gmail.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
3 PACS
Support Handbook
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
• Hot-fixes (or) T24 Updates that have been applied on top of the base release or SP
• Operating System
(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.
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.
For e.g.
Monday – Info requested from Client - 1 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.
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
8 PACS
Support Handbook
9 PACS
Support Handbook
10 PACS
Support Handbook
Account
Account Related Problems
Discrepancy in Account Balance
String : String :
String : String :
Replace XXX with respective mnemonic of the company and ZZZ with problematic account number
>SELECT FXXX.STMT.PRINTED WITH @ID LIKE "ZZZ..." >SELECT FXXX.STMT.PRINTED WITH @ID LIKE "ZZZ..."
11 PACS
Support Handbook
Replace XXX with respective mnemonic of the company and ZZZ with problematic account number
12 PACS
Support Handbook
• AZ.ACCOUNT record.
• AZ.SCHEDULES record.
• Output of the ENQ STMT.ENT.BOOK for the AZ.ACCOUNT, NOMINATED and REPAY accounts where ever applicable.
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.
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.)
3. Database used for ARC Mobile –(MySQL, Oracle, MSSQL server, etc.)
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”)
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.
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
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)
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
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
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
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.
19 PACS
Support Handbook
Scenario: 1
If the problem is at Head office server provide us with the below information.
Scenario: 2
If the problem occurred in Branch Server provide us with the below information.
20 PACS
Support Handbook
Cheque.Collection
For all CHEQUE.COLLECTION related problem, provide us
21 PACS
Support Handbook
COLLATERAL
COLLATERAL - TAFC Compliance
For All Problems
● COLLATERAL
● COLLATERAL.RIGHT
● All Related LIMIT records
● LIMIT
● COLLATERAL
● COLLATERAL.RIGHT
● Full view of the LIMIT.COL.ALLOC.WORK record specified in the ALLOC.WORK.ID in the
corresponding LIMIT record
jsh-->TERM 300
jsh-->SEARCH FXXX.LIMIT.COL.ALLOC.WORK
String :<cust.no>
String :
Record Keys : *
(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
22 PACS
Support Handbook
(D)
jsh-->TERM 300
(E)
(F)
(G)
Replace <cust.no> with customer id involved seen in the crash or hang or mw42 or show-item-locks
● LIMIT
● COLLATERAL
● COLLATERAL.RIGHT
● Full view of the LIMIT.COL.ALLOC.WORK record specified in the ALLOC.WORK.ID in the
corresponding LIMIT record
23 PACS
Support Handbook
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
2. BNK/CM.FIND.MATCH.MESSAGE
R11 service:
BNK/MB.CM.FIND.MATCH.MESSAGE
WORK FILES:
Two work files used in Confirmation Matching application are as follows:
25 PACS
Support Handbook
>TERM 400
>QSELECT FXXX.STMT.PRINTED
Replace XXX with respective mnemonic of the company and ZZZ with problematic account number
5. Full view of respective ENQUIRY record used in above PRINT.STATEMENT for statement format
Sweeping
From Classic Prompt,
26 PACS
Support Handbook
From jBASE
>TERM 400
>QSELECT FXXX.STMT.PRINTED
Replace XXX with respective mnemonic of the company and ZZZ with problematic account number
Cash Pooling
From Classic Prompt,
From jBASE
>TERM 400
>QSELECT FXXX.STMT.PRINTED
Replace XXX with respective mnemonic of the company and ZZZ with problematic account number
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
1.>TERM 300
>QSELECT Fxxx.RE.CONSOL.ACCOUNT
27 PACS
Support Handbook
2>TERM 300
In R06
AC.1.TR.GBP.1003.3000.GG.205.No.50000 0.03 0.01 0.02
1.>TERM 300
>QSELECT Fxxx.RE.CONSOL.ACCOUNT
2.>TERM 300
>QSELECT FBNK.RE.CONSOL.ACCOUNT
3.>TERM 300
4.>TERM 300
1>TERM 300
>QSELECT FXXX.RE.CONSOL.CONTRACT
2>TERM 300
>QSELECT FXXX.RE.CONSOL.CONTRACT
3>TERM 300
28 PACS
Support Handbook
4>TERM 300
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
29 PACS
Support Handbook
a)
>TERM 300
b)
>TERM 300
>QSELECT FXXX.STMT.PRINTED
c)
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
IC.COB performance
> LIST F.SPF
31 PACS
Support Handbook
LIMITS
For all Problems
Provide records from the following files:
Discrepancy between the value of TOTAL.OS in LIMIT and Forex outstanding amount
FOREX
LIMT.DAILY.OS
32 PACS
Support Handbook
jsh-->TERM 300
jsh-->SEARCH FXXX.LIMIT.COL.ALLOC.WORK
String :<cust.no>
String :
Record Keys : *
(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
(D)
jsh-->TERM 300
33 PACS
Support Handbook
(E)
(F)
(G)
Replace <cust.no> with customer id involved seen in the crash or hang or mw42 or show-item-locks
CONSOLIDATE.ASST.LIAB
LL
0 LK ...<CAL ID>...
>QSELECT FXXX.RE.CONSOL.CONTRACT
>LIST FXXX.LIMIT
b) jsh->TERM 300
34 PACS
Support Handbook
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
36 PACS
Support Handbook
sqlplus
sql>quit
37 PACS
Support Handbook
JDLS Issues
Information Required for All Issues
jDLS –dvL
Server architecture
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.
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.
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
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.
From R08 and higher releases, you need to use the enquiry DE.HANDOFF.DETS to get the handoff information
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
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.
4. In case the problem is with incoming message, the actual incoming message
5. DE.INTERFACE records
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
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
In case of Universe,
In case of jBASE,
jshow–c <>
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
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
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
Tcserver.xml
Global.log
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
DE.O.PRI.FORMS.SPOOL
DE.O.PRI.FORMS
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 ,
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
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
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
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
DE.I.HEADER/DE.O.HEADER
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
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
DX Online issue
DX.TRADE
Related DX.TRANS.KEYS
Related DX.TRANSACTION
Related Its DX.REP.POSTION
Related STMT.ENTRY
45 PACS
Support Handbook
FATCA
For all FATCA related problems
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
b) If the problem is specific to Browser send the details requested in Browser chapter
a) TRANS.JOURNAL (TRANS.JOURNAL2 –Prior to R8 / TXN.JOURNAL.PRINT – From R8) for the respective date
c) RE.CONSOL.FOREX (for releases lesser than R08) / EB.CONTRACT.BALANCES (for releases above R08)
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.
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
a) DE.MESSAGE, DE.MAPPING, DE.FORMAT.SWIFT of the related MTnnn (300, 103, 202 etc…) message
c) In Database level run SEE.HANDOFF; enter Delivery key as for the DE.O.HEADER, e.g. SEE.HANDOFF
D2005020400005082700
7) FX NETTING
a) NETTING.PARAMETER
b) NP.CONCAT
48 PACS
Support Handbook
c) NETTING.ENTRY
d) NETTING
49 PACS
Support Handbook
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
a) Then TRANS.JOURNAL (TRANS.JOURNAL2 –Prior to R8 / TXN.JOURNAL.PRINT – From R8) of the respective date.
b) All the accounting entries.
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
(2) T24 Browser release (To check (i) Login to T24 Browser (ii) Click "Help" link (iii) Click "About Browser" ).
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
(For ex )
51 PACS
Support Handbook
Jsh-->sh
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
################################################################################
log4j.appender.logFile=org.apache.log4j.RollingFileAppender
log4j.appender.logFile.layout=org.apache.log4j.PatternLayout
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 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
################################################################################
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.
(2) T24 Browser release (To check (i) Login to T24 Browser (ii) Click "Help" link (iii) Click "About Browser" ).
52 PACS
Support Handbook
a. Set the log level to DEBUG in the TAFJTrace.properties present under the 'conf' directory of TAFJ home directory.
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.
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
################################################################################
log4j.appender.logFile=org.apache.log4j.RollingFileAppender
log4j.appender.logFile.layout=org.apache.log4j.PatternLayout
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 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
################################################################################
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
With TCServer
tcserver.xml & environment.vars files from the \tcserver\conf directory
With JCA
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".
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".
TAFJ ARCHITECTURE
All the Application Server(JBOSS/WebSphere/WebLogic) logs
55 PACS
Support Handbook
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.
If TWS(EE)
1. a)The version of TWS(EE) used
3. a)The log files for the project and detailed jbase_agent log (starting jbase_agent in –L mode)
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
3. b)The log files from both project log and T24Service Connector log Folder
6.b)The enquiry/Version record used if problem faced in web service creation. Corresponding PW.ACTIVITY and EB.SERVICE record
from T24
If TWS(EE)
1. a)The version of TWS(EE) used
3. a)The log files for the project and detailed jbase_agent log (starting jbase_agent in –L mode)
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
3. b)The log files from both project log and T24Service Connector log Folder
6.b)The enquiry/Version record used if problem faced in web service creation. Corresponding PW.ACTIVITY and EB.SERVICE record
from T24
Following listings
>TERM 800
58 PACS
Support Handbook
FT.LOCAL.CLEARING record
FT.BC.PARAMETER record
FUNDS.TRANSFER record
FT.CHARGE.TYPE record
FT.COMMISSION.TYPE record
FT.APPL.DEFAULT record
FT.GROUP.CONDITION record
CUSTOMER.CHARGE record
FUNDS.TRANSFER record
FT.GROUP.CONDITION record
CURRENCY record.
FT.APPL.DEFAULT record
COMPANY record
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
FUNDS.TRANSFER record
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
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
Balance mismatch in MD
For balance mismatch, supply us with details of STMT.ENTRY, CATEG.ENTRY and RE.CONSOL.SPEC.ENTRY.
MD.PARAMETER
MD.DEAL
MD.BALANCES
EB.CONTRACT.BALANCES
61 PACS
Support Handbook
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
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
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.
a) >TERM 300
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
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.
5) If COB crashes
a) Respective COMO
b) Full view of all history records for the MM deal shown in crash
a) SHOW-ITEM-LOCKS
b) WHERE (V
c) mw42
e) Full view of all history records for the first MM deal in the joblist
c) In Database level run SEE.HANDOFF; enter Delivery key as for the DE.O.HEADER, e.g. SEE.HANDOFF
D200502040000508270
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.
Unprocessed schedules
MG.MORTGAGE
MG.BALANCES
EB.CONTRACT.BALANCES
ENQ STMT.ENT.BOOK for the MORTGAGE account.
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
66 PACS
Support Handbook
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
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.
Account overdrawn by PD
PD contract
ENQ STMT.ENT.BOOK
PD.PARAMETER
ACCOUNT record.
ACCOUNT.PARAMETER record.
LIMIT record of Corresponding PD
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.
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
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.
71 PACS
Support Handbook
Reporting
Balance Mismatch
Balance Mismatch Messages – IC Mismatches
1. Full view of below CAL records from the problematic company
jsh->TERM 300
jsh->COMO ON SPEC.LIST
>QSELECT FXXX.RE.CONSOL.SPEC.ENT.KEY
>COMO OFF
>TERM 300
>COMO ON SPEC.DETAIL.LIST
>QSELECT FXXX.RE.SPEC.ENTRY.XREF
>COMO OFF
>TERM 300
>COMO ON ACCT.LIST
>QSELECT FXXX.RE.CONSOL.CONTRACT
>COMO OFF
>TERM 300
>COMO ON ECB.LIST
>COMO OFF
>TERM 300
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
>TERM 300
>TERM 300
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
Where
73 PACS
Support Handbook
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. 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.
1. jshow -c RE.OUTPUT.EXTRACT
4. Below listings
jsh->TERM 600
jsh->TERM 600
jsh->TERM 600
RCA Entry
1. Full CRF detailed 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
74 PACS
Support Handbook
4. Below counts
jsh->COUNT Fxxx.RE.STAT.LINE.BAL
jsh->COUNT Fxxx.RE.STAT.LINE.MVMT
Post Closing
PC adjustment is not reflecting in Report
3. Sample adjustment transaction by FT / DC which is to adjust the report line balance in PC report
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.
>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
2) Creation of Entitlements while doing through Phantom/Service (available from T24) even if the SECURITY.POSITION exist, then
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)
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:
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
78 PACS
Support Handbook
79 PACS
Support Handbook
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
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
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
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
Syndicated Loans
Balance mismatch in SL - TAFC Compliance
For balance mismatch, supply us with details of
82 PACS
Support Handbook
PRE.SYNDICATION.FILE
FACILITY
SL.LOANS
SL.PARAMETER
83 PACS
Support Handbook
84 PACS
Support Handbook
System Core
System Core - TAFJ Compliance
Any TAFJ related issues, our first requests are as follows.
2. TAFJTrace.properties – to know about the logs enabled/disabled and request for enabling/disabling.
4. Full view of the F.SPF>SYSTEM record to know the current release and list of updates installed so far
6. >tdiag or >tDiag –cf tafj.properties to know the overall settings of the system
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.
85 PACS
Support Handbook
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
In order to extract the thread COMO for each of the individual session, execute the below command from Universe/jBASE prompt
3. The batch COMO may also be extracted by running the main line routine MERGE.GUI.COMO from the Awaiting Application
prompt.
To get the Process Name, eliminate “<<Company.Mnemonic>>/ ” if present, from the BATCH record id.
86 PACS
Support Handbook
▪ F.BATCH.STATUS record for the crashed batch process. The id of the F.BATCH.STATUS record will be of the format.
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)
SYSTEM.END.OF.DAY3-PROC.REVAL.STATIC.CHANGE-1
0001 FBNK.JOB.LIST.4
>
Eg :
ERROR
0001 AC.STMT.UPDATE*PRINT.ACCOUNT.STMT
LIST F.EB.EOD.ERROR WITH @ID LIKE …<<date when the crash had occurred>>…
CURRENT.SERVICE. COB
NEXT.SERVICE.... STOP
COMO.NAME....... tSA_4_1367043998
JOB.PROGRESS.... 3
LIST F.EB.EOD.ERROR WITH @ID LIKE …<<date when the crash had occurred>>…
87 PACS
Support Handbook
2. Full COMO of the crashed agent. This can be obtained from the file F.TSA.STATUS in the field COMO.NAME
CURRENT.SERVICE. COB
NEXT.SERVICE.... STOP
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.
88 PACS
Support Handbook
jshow -c DM.GET.LIST.DOCUMENTS
89 PACS
Support Handbook
>TERM 300
>TERM 300
a. GETDBNAME F.SPF
b. DESCRIBE F_SPF
c. DESCRIBE D_F_SPF
d. DESCRIBE TAFJV_F_SPF
90 PACS
Support Handbook
a. Database.log
b. Runtime.log
c. Execute.log
d. Sqltrace.log
• 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.
• Output of corresponding resource screenshot from source tab. Example .version in case the issue is with importing/exporting Version
record.
91 PACS
Support Handbook
Issue TWS(EE)
1. plugin version of TWS(EE) used
3. Following information required in case the issue in creating the TWS project(war file)
Full view Enquiry/Version record used and the corresponding PW.ACTIVITY and
4. Clear the TAFC\log directory, replicate the issue and send us the newly created TAFC\log.
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.
9. Capture the OFS request in the server/application log and process the same using tSS and send us the output.
Issue in TWS(.NET)
1. The version of TWS(.NET) used and Visual Studio Version.
3. b)The log files from both project log and T24ServiceConnector log Folder
6.b)The enquiry/Version record used if problem faced in web service creation. Corresponding PW.ACTIVITY and
EventDesigner(EE) – Java
Error message in the console window in case of issue in publishing the event to T24.
EventDesigner(EE) – Java
92 PACS
Support Handbook
3. Error message in the console window in case of issue in publishing the event to T24.
EventDesigner(.NET)
3. Error message in console window in case of issue in publishing the event to T24.
• 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.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
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:
93 PACS
Support Handbook
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:
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.
94 PACS
Support Handbook
Note: jcheck and jrf are to be performed at a time when no other process is accessing the file.
• SHOW-ITEM-LOCKS
• truss –o truss.out –p <process id on the session where the problem is recreated> (Unix only)
• mw42 -m
Note 1: All these details need to be collected in parallel when 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).
Output of commands
SP-STATUS
jsp_scan –v
Status of printing from OS level
•jlicenseinfo –pt
95 PACS
Support Handbook
A copy of ‘system.properties’ file from the ‘config’ directory of jBASE installation directory.
• jInstallKey -v
• jInstallKey –v
• jdiag –dvL
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
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
################################################################################
log4j.appender.logFile=org.apache.log4j.RollingFileAppender
log4j.appender.logFile.layout=org.apache.log4j.PatternLayout
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 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
################################################################################
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.POST.MESSAGE
• OFS.CONNECTION.MANAGER,
• tSS
98 PACS
Support Handbook
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.
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
100 PACS
Support Handbook
CONDITION.PRIORITY record
From jBASE
----àCT FXXX.XX.GEN.COND.PRTY where XXX is the company mnemonic and XX is the related application id
From jBASE
>LIST FXXX.TAX.GEN.CONDITION
>LIST FXXX.TAX.TYPE.CONDITION
>LIST FXXX.TAX.GEN.COND.PRTY
101 PACS
Support Handbook
Replace XXX with company mnemonic & <<CUS.ID>> with problematic Customer.
CONDITION.PRIORITY record
From jBASE
----àCT FXXX.XX.GEN.COND.PRTY where XXX is the company mnemonic and XX is the related application id
From DBTools
>LIST-ITEM FXXX.TAX.GEN.CONDITION
>LIST-ITEM FXXX.TAX.TYPE.CONDITION
>LIST-ITEM FXXX.TAX.GEN.COND.PRTY
102 PACS
Support Handbook
Replace XXX with company mnemonic & <<CUS.ID>> with problematic Customer.
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
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".
Send the version of java by typing the below command in jshell prompt
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 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
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
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
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.
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.
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 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:
If a TEMENOS consultant is on-site, they will require use of a PC, printer and telephone.
Licensing Issue
For Maintenance Code Request
Full view of SPF record
Date until which we need to issue the Maintenance code.
108 PACS
Support Handbook
If Browser,
If TCServer,
If JBOSS,
a. t24-ds.xml file
b. browser.log
2. Jdiag
5. If Browser,
If Browser,
If TCServer,
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 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
110 PACS
Support Handbook
jsh-->SP-STATUS
jsh-->cd $JBCSPOOLERDIR
jsh-->jstat -v jspool_log
jsh-->jdiag
111 PACS
Support Handbook
Replace XXX with respective mnemonic of the company and purge.date with the archive PURGE.DATE
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
jsh-->tar
jsh-->gtar
112 PACS
Support Handbook
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
After running BNK/T24.UPDATES service, SPF not updated or data records pertaining to that update not released:
CT SYSTEM TEMP.RELEASE
jsh-->COUNT %F.SL
jsh-->echo $JEDIENABLEQ2Q
jsh-->echo $JEDIFILENAME_SYSTEM
jsh-->jstat -v SYSTEM
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’
CT F.PGM.DATA.CONTROL ‘F.BATCH>COB.INITIALISE’
CT F.RELEASE.DATA ‘F.XXX>YYY’
CT VOC MB.CLIENT
114 PACS
Support Handbook
CT F.PGM.DATA.CONTROL ‘F.XXX>YYY’
CT F.RELEASE.DATA ‘F.XXX>YYY’
3. TAFJ or TAFC –
5. Application server used along with Version number - (JBoss 5, WebSphere 7.1, etc..)
8. Steps to replicate (if applicable)– (1. Login TCIB application, 2.Click Move money, 3. Transaction failed displaying “XYZ”)
115 PACS
Support Handbook
3. TAFJ or TAFC –
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.
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.
116 PACS
Support Handbook
117 PACS
Support Handbook
Trade Finance
LETTERS.OF.CREDIT
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 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
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
LC.PARAMETER
LETTER.OF.CREDIT
DRAWINGS
LC.BALANCES(IF APPLICABLE)
EB.CONTRACT.BALANCES
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
b) SWAP.SCHEDULES
e) The HOLIDAY records for the Business centres, local currency and the currencies traded.
a) The TRANS.JOURNAL (TRANS.JOURNAL2 –Prior to R8 / TXN.JOURNAL.PRINT – From R8) of the respective date.
c) RE.CONSOL.SWAP (for releases lesser than R08) / RE.CONSOL.CONTRACT and EB.CONTRACT.BALANCES (for
releases above R08)
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
f) CURRENCY records
a) SWAP
PROVISION
120 PACS
Support Handbook
IBAN generation
1. Full view of the ACCOUNT record and screenshot of any error while creating account
121 PACS
Support Handbook
EDGE
EDGE
1. Basic 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.
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
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
4. SPF record.
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
123 PACS