Question

Why is the bank account updated incorrectly after interest CAP while using value dated
accounting system?

Answer

Always in a bank IC should follow trade dated accounting. Do the changes in

ACCOUNT.PARAMETER from bank end and make IC as trade dated.

Question

Why is the error ‘** FATAL ERROR IN (OPF) ** NO FILE.CONTROL RECORD - F.XXX ,
MNEMONIC =’ being displayed on trying to login after running EB.COPY.GLOBUS.JBASE ?

Answer

After running EB.COPY.GLOBUS.JBASE, you need to run T24.PRE.RELEASE before running

GLOBUS.RELEASE. This program will copy the missing files in the upgraded version that is
required during logon. This will ensure that there are no crashes during logon for doing
GLOBUS.RELEASE. If not kindly run the program T24.PRE.RELEASE from jbase prompt

Question

Why is the following error message ‘IDESC field XXXX with Subroutine type is Incompatible
with J24’ displayed when authorising the SS record?

Answer

IDESC is to be removed in the higher releases, instead J descriptors are going to be used
for some fields and others are being modified to select from inside the routine itself. Hence
the system will raise an override if it finds any IDESC field called with SUBR. This check is
only for higher release java compatible code.

IDESC are dynamic fields which are not actually data fields and they get the data at run
time. This will form part of dict and can be used by select command in other places like
normal data field. These fields are more JQL dependent fields and not supported in the SQL.
So any IDESC that is used directly on select queries has to be replaced suitably. This is a
new enhancement for higher release

Question

How to resolve the problem of I/O ERROR in SP-STATUS when printing?

Answer

In general, the 'I/O error' in SP-STATUS menu will occur for the following reasons:
I. No proper (working) printer is assigned
II. If the path of the device is not valid
III. If there is any interference between the system and the physical printer.
Rectify the mentioned problems if present in your system and try printing again. Note that
you can refer to:
a) Take a Backup of the jspooler Directory
As root user run:
SP-SHUTDOWN
SP-NEWTAB
Note that the above commands require jBASE environment to be set - hence please run
.profile (present in bnk.run directory)
prior to executing these commands. Choose the default path which is '/usr/jspooler' and
press 'C'.
b) Attach network-friendly flag to the jspool_log file as shown below
jsh~-->cd $JBCSPOOLERDIR
jsh~-->jchmod +N jspool_log
c) Now re-create your QUEUES.

Question

How to identify active users/sessions in T24?

Answer

The file F.OS.TOKEN contains tokens of the active users currently logged in T24. An enquiry
can be created based on this file.

Question

How to know/check the activities done by a USER on a day?

Answer

The file F.PROTOCOL contains the activities done by a user. The REPGEN report PROTOCOL
will generate a report which contains the list of activities done on a day.

Question

What is the setup for “Daylight time saving” in T24?

Answer

There is no specific configuration required in T24 for day light saving. The timing changes
done at the server level will be reflected in the T24 system.

Question

How to avoid error during resizing of empty files?

Answer

When we do resizing of files, we may include empty files also. The following error could
occur:
jrf -S101 TESTFILE
/opt/apps/dev/globus/DEV01/t24dev/bnk.run/TESTFILE is currently an empty file
(R)esize anyway or (S)kip file resize :
To suppress the above error prompt, kindly use the -E option to suppress the system from
raising the prompts as shown below:
jsh ->jrf -E -S101 TESTFILE

Question

What is the procedure for Archiving delivery related files in R06?

Answer

ARCHIVING PROCESS It is recommended that the archiving process is run after the end of
day has been completed, but before users are allowed to sign on. However, since archiving
removes data, which is no longer used, it can be run whilst the system is being used. The
system on which archiving is run should be fully backed up to tape. It is important to note
that archiving is a one-way process: data cannot be restored afterwards, except by fully
restoring the database back to the point of pre-archiving.

DELIVERY ARCHIVING: Functionality: Archive records from the related delivery files to the
standard $ARC files. 1.Records on DE.x.HEADER.ARCH older than the Purge date will be
moved from DE.x.HEADER.ARCH to DE.x.HEADER$ARC (x denotes "O" or "I”, Outward or
Inward). 2.The records will be moved from DE.x.HISTORY to DE.x.HISTORY$ARC and the
entry will be moved from the file DE.x.HISTORY.QUEUE to DE.x.HISTORY.QUEUE$ARC.
3.Before Archiving the Delivery file we should run the DE.MM.O.END.OF.PERIOD. It will
move the record from the DE.x.HEADER to DE.x.HEADER.ARCH. The program
DE.MM.x.END.OF.PERIOD should be run from Awaiting Application Prompt in T24.
ARCHIVING PROCEDURE (ARCHIVE): Simple Step for Delivery Archiving for Outward
Message: 1. Set the field MAINTAIN HISTORY in DE.PARM record to ‘Y’. Then go to
Application prompt, type DE.MM.O.END.OF.PERIOD. Before running this application close all
the delivery related phantoms. 2. It will ask to Enter the ARCHIVE DATE. (For Example
20031201 if December is the current Month) (Records older than this date is archived) 3.
Then it will ask you to Continue, press Y 4. It will update some record in this stage. 5. Go
Once again to the Application Prompt, type ARCHIVE L 6. Take the Delivery record and run
in Verify mode. ie. V 7. Commit the Record. 8. Enter the Field no.2. (For example
PURGE.DATE........ 20031201) 9. Set the Retention Period to Blank. ie. Field no.3 10.
Commit the record. 11. It will displaythis message "All records before 20031201 will be
purged" 12. Press Y to continue this step. 13. Clear the handoff file by specifying next run
date for the job DE.MM.CLEAR.HANDOFF in the BACTH entry CUS.TIDY.UP. 14. Delivery
Archiving is completed now. Same procedure is followed for Inward Message except
DE.MM.I.END.OF.PERIOD will be run in Step 1. The date criteria for Archival can be specified
in two different ways 1. Purge.date: Records older than this date will be archived and/or
deleted. 2. Retention.period: This Field is used as an alternative method of specifying the
purge date in the format nnM or nnY, where nn is a number of either Months or Years.
Records older than the retention period will then be archived. For example if today's date is
01/12/2003 and a retention period of 3 months is specified (3M), three months is calculated
from the beginning of the month. Therefore, any records before 1/9/2003 will be archived.
This field will only be used if PURGE.DATE is null. HOW TO RUN 1. Set the field MAINTAIN
HISTORY to “Y”. DE.PARM RECORD TEMENOS MODEL BANK DE.PARM SEE ID................
SYSTEM.STATUS ---------------------------------------------------------------------- 7. 6
OUTWARD CARRIER RECS 8. 6 SHUT OUT CARR.. C 9 READ PRIORITY..... 10 10 READ
NORMAL....... 10 11 DISP CONTROL...... Y 12 INWARD ROUTING.... Y 13 MAINTAIN
HISTORY.. Y 15 MACHINE.ID........ ST400 16 SWIFT MF SEQUENCE. 1 17 SWIFT SF
SEQUENCE. 1 18 SWIFT.HARDWARE.... ST400 19 SWIFT.PROTOCOL.... 3270 20
SWIFT.NETWORK..... 2 26 TELEX SF SEQUENCE. 1 27 TELEX LINE NO..... 1 28 TELEX
HARDWARE.... UNITELEX ---------------------------------------------------------------------- 24
MAR 2005 12:47:01 USER (01 NOV) SUBA2 [18,7] PAGE 2 ACTION AWAITING PAGE
INSTRUCTIONS 2. DE.MM.O.END.OF.PERIOD TEMENOS MODEL BANK OUTWARD END OF
PERIOD PROCESS ---------------------------------------------------------------------- 1
ARCHIVE.DATE...... 01 DEC 2000 2. 1 LOCAL.REF...... 3 RESERVED.3........ 4
RESERVED.2........ 5 RESERVED.1........ 6. 1 OVERRIDE....... 7 RECORD.STATUS..... 8
CURR.NO........... 9. 1 INPUTTER....... 10. 1 DATE.TIME...... 14 FEB 07 02:55 11
AUTHORISER........ 7_NITHYA.1 12 CO.CODE........... US-001-0001 BNK R05BASE 13
DEPT.CODE......... 14 AUDITOR.CODE...... 15 AUDIT.DATE.TIME...
---------------------------------------------------------------------- 25 FEB 2005 11:10:26 USER
(10 MAY) STEPHENSMITH1 [48,tM] ACTION ENTER ARCHIVE DATE OR TO TERMINATE The
above process will move the records from DE.O.HEADER to the archive file (i.e.,
DE.O.HEADER.ARCH). >COUNT F.DE.O.HEADER.ARCH è This will give the count of no. of
messages in the ARCH file. 3. Run the ARCHIVE application in VERIFY mode: TEMENOS
MODEL BANK Archiving SEE ARCHIVE.ID........ DELIVERY
--------------------------------------------------------------------------- 1. 1. 1 GB DESCRIPTN
Archive delivery history files: 1. 2. 1 GB DESCRIPTN DE.x.HEADER.ARCH, DE.x.HISTORY, 1.
3. 1 GB DESCRIPTN DE.x.HISTORY.QUEUE 2 PURGE.DATE........ 01 DEC 2000 3
RETENTION.PERIOD.. 01M 4 ARCHIVE.DATA...... Y 6. 1 ARC.FILENAME...
DE.O.HEADER$ARC 6. 2 ARC.FILENAME... DE.O.HISTORY$ARC 6. 3 ARC.FILENAME...
DE.O.HISTORY.QUEUE$ARC 6. 4 ARC.FILENAME... DE.I.HEADER$ARC 6. 5 ARC.FILENAME...
DE.I.HISTORY$ARC 6. 6 ARC.FILENAME... DE.I.HISTORY.QUEUE$ARC 9
STOP.INDICATOR.... NO 10 CHECK.NO.OF.RECS.. 1000 11 ROUTINE........... ARC.DELIVERY
12. 1 COMPANY.RUN.IN. US0010001 TEMENOS MODEL BANK 13. 1 TIME.STARTED... 13
MAR 03 12:11 14. 1 USER.ID........ 23_MICHAELEVANS1 15. 1 DATE.SELECTED.. 01 DEC
2000 16. 1 STOP.REQUESTED. NO 17. 1 RECS.DELETED... 14 18. 1 RECS.PROCESSED. 14
20. 1 TIME.ENDED..... 13 MAR 03 12:11 12. 2 COMPANY.RUN.IN. US0010001 TEMENOS
MODEL BANK 13. 2 TIME.STARTED... 13 MAR 03 12:04 14. 2 USER.ID........
23_MICHAELEVANS1 15. 2 DATE.SELECTED.. 01 DEC 2000
-------------------------------------------------------------------- 13 MAR 2003 12:24:18 USER
(13 DEC) MICHAELEVANS1 [23,tn] PAGE 2 ACTION AWAITING PAGE INSTRUCTIONS
>COUNT F.DE.O.HEADER.ARCH 0 records counted. > 4. CLEARING F.DE.O.HANDOFF FILE
Then to clear the handoff file before you start the BC you should amend the BATCH record
for the BATCH job CUS.FILE.TIDY.UP as shown below. (i.e., run the BATCH job
DE.MM.CLEAR.HANDOFF for this day alone, from the batch process CUS.FILE.TIDY.UP, in
the start of day. For this the NEXT.RUN.DATE in the batch job has to be set to the
NEXT.WORKING.DATE.) BATCH record which has to be amended before starting the EOD, In
order to clear the HANDOFF. MODEL BANK BATCH ENTRY SEE BATCH PROCESS.....
CUS.FILE.TIDY.UP --------------------------------------------------------------------------- 1
BATCH.STAGE....... D002 START OF DAY 3 PROCESS.STATUS.... 0 READY 4
BATCH.ENVIRONMENT. F FOREGROUND 6. 1 JOB.NAME....... DE.MM.CLEAR.HANDOFF 8. 1
FREQUENCY...... D DAILY 9. 1 NEXT.RUN.DATE.. 03 JUL 2001 12. 1 JOB.STATUS..... 0
READY 13. 1 LAST.RUN.DATE.. 23 DEC 1994 6. 2 JOB.NAME....... NOSTRO.PURGE 8. 2
FREQUENCY...... D DAILY 9. 2 NEXT.RUN.DATE.. 03 JUL 2001 12. 2 JOB.STATUS..... 0
READY 13. 2 LAST.RUN.DATE.. 02 JUL 2001 6. 3 JOB.NAME....... DE.PURGE.DIV.FILES 8. 3
FREQUENCY...... D DAILY 9. 3 NEXT.RUN.DATE.. 03 JUL 2001
--------------------------------------------------------------------- 18 MAR 2003 15:03:38 USER
(02 JUL) INPUTTER [21,tk] PAGE 1 >>>2>>> ACTION AWAITING PAGE INSTRUCTIONS Ø
Dates record MODEL BANK DATES - DEFAULT LIST ID TODAY VERSION LAST.WORKING.DAY
NEXT.WORKING.DAY FUNCT.
---------------------------------------------------------------------- 1 US0010001 02 JUL 2001 1
29 JUN 2001 03 JUL 2001 ----------------------------------------------------------------------
18 MAR 2003 15:06:31 USER (02 JUL) INPUTTER [21,tk] PAGE 1 >>>1>>> ACTION
AWAITING PAGE INSTRUCTIONS NOTE:- STOP.INDICATOR: Flag to halt the archiving
process. This field is checked after the number of records specified in
CHECK.NO.OF.RECORDS that has been processed. If this field is set to "Y" while the
Archiving process is being run, the archiving will come to a controlled halt. Values in this
field can be Y or NO. Default NO. CHECK.NO.OF.RECS: Number of records processed each
time before the STOP.INDICATOR is checked. If this field is set too low, it will slow down the
archiving process as this record will continually be read from the archive file to see if a stop
has been requested. If it is set too high, the archiving process will take a long time to stop
as there will be long intervals between the checking of this flag. This field may be changed
while archiving is running and will take effect the next time the record is checked (i.e. after
the current block of records has been processed). The Suggested values for Delivery is as
follows. The check number of records field refers to the DE.O.HEADER.ARCH and
DE.I.HEADER.ARCH files. Processing for each record is fairly simple, so the check number of
records field should be set fairly high. A figure of 1,000 is suggested which can be changed
on-line if necessary.

Question

Are delivery services required for each company, e.g. Is CO2/SWIFT.IN needed?

Answer

No, company wise SWIFT.OUT/SWIFT.IN service is not required. When ever a delivery
message is generated the DE.O.HEADER/DE.I.HEADER will be updated with the relevent
COMPANY details. If there are no mapping errors then the Activation file will be updated
accordingly. Based on the details in DE.O.HEADER/DE.I.HEADER the SWIFT.OUT/SWIFT.IN
service the process the messages accordingly.

Question

Why did the COB crash in the JOB-DC.BATCH.COB of the BATCH-BNK/EOD.DATA.CAPTURE?

Answer

The Internal ACCOUNT records that are required by GLOBUS applications must exist prior to
entering any transactions on these applications. As these accounts were not created, it
resulted in the crash. So please create internal accounts for local currency as required by
GLOBUS. These are listed in the ACCOUNT.CLASS records and are detailed in the field
RECORD.TYPE.

It is recommended that the local currency ACCOUNT records be input manually. GLOBUS is
able to open any foreign currency ACCOUNT required automatically, providing that one
exists for the specific ACCOUNT category.

Question

How do we supress Overrides in ARC-IB ?

Answer

Set AUTO in TYPE field in OVERRIDE application.

Question

Why residual entries are still present in the JOB.LIST file though the job says completed?
Additionally, ’Job finished by another thread’ in the COMO records can be seen.

Answer

You need to check whether 'ROLLBACK' flag is set to 'NO' [see 'jstat -v' output of these
files] for files like F.TSA.STATUS and F.BATCH.STATUS.

From a technical perspective, if ROLLBACK is set as ‘NO’, the lock acquired on the file gets
released immediately when WRITE is encountered on the file rather than getting released at
the close of a transaction boundary.

From an application perspective, the expected functionality is that a) the lock is acquired on
the F.BATCH.STATUS file, b) transaction boundary is started, c) population of
F.BATCH.STATUS, d) population of JOB.LIST is done and e) transaction boundary. Because
the lock is getting released before encountering the transaction boundary, the agents which
are supposed to wait on the lock of F.BATCH.STATUS, selects the JOB.LIST file (which is
while the system is in the process of populating the JOB.LIST) sees that there are no
records to process and marks the job to completed. As one agent marks this as
“Completed”, all other agents also mark as “Completed” thus leaving residual entries in the
JOB.LIST.

Sites running jBASE Transaction Journaling, in an attempt to control the rapid growth of
logsets, suspend logging of unwanted files [files that are NOT required at DR site like
F.OS.TOKEN, F.ENQUIRY.LEVEL, F.BATCH.STATUS etc]. This is achieved by forcing '-T' and
'-L' flags [removing Transaction management and Transaction Journalling flags] on these
files. Normally, only '-L' is required to suspend logging but since the updates are from T24,
the entry will be recorded in the TJ logset as everything happens inside a transaction
boundary within T24. This is because updates within a transaction boundary are usually
multiple transactions, and hence this logging is controlled by the ‘+T’ flag on the file. So, in
order to ‘really’ disable logging for such unwanted files it was required that we need to run
‘jchmod -T’ also -
jchmod -L -T <file name>

Now the '-T' flag on F.BATCH.STATUS and F.TSA.STATUS has resulted in updates on these
files not respecting the transaction boundary. Hence we see locks getting released
immediately after the WRITE and even before TRANSEND and resulting in unprocessed
contracts during COB.

Going forward, as a solution to the existing problem, we request you to revert the settings
on the affected files to solve this issue.

Hence please run the below commands and retest the COB to see if further the problem of
leaving behind unprocessed contracts resurfaces.
jchmod +T F.BATCH.STATUS
jchmod +T F.TSA.STATUS
jchmod +T F.TSA.SERVICE
Because of changing the ROLLBACK from “-T” to “+T”, your log size may increase by a small
scale if you use TJ. But there will not be any performance impact because of this.

Question

How to solve the WRITE_ERROR to F_REPGEN_CREATE file?

Answer

NEED TO CHECK:
ORAdriver log error with corresponding time stamp.
T24 level solution:
1. Stop TSM and all Other agents.
2. Restart the TSM and COB agents.
Oracle level Solution:
If oracle error is ORA-24813 then it means system cannot send or receive an unsupported
LOB
Cause: An attempt was made to send a LOB across the network, but either the server does
not support the LOB sent by the client, or the client does not support the LOB sent by the
server. This error usually occurs when the client and server are running different versions of
Oracle.

Action: Use a version of the Oracle that supports the LOB on both the client and the server

Question

When and how should an index be created on a field?

Answer

You can index a field which is frequently queried upon. While creating the index make sure
that -
1) Index is created under 'en_US' locale for better performance [applicable for pre-jBASE
4.1.5.22 and jBASE 5.0.10 releases]
2) Index is created with '-w' option wherever possible [The index updating can be made
faster by creating the index in Permanent write mode. The ‘-w’ option causes the index to
have a subtly different internal structure, which can improve the update / creation time in
some circumstances (depending on the actual contents of the indexed fields, number of
different values etc).]
3) Always create a 'L'eft justified index for a 'L'eft justified field and 'R'ight justified index for
a 'R'ight justified field. Use 'BY-AL' and 'BY-AR' clauses accordingly. Use 'LIST-INDEX -av
<filename>' to view index properties.

Question

Are there any recommendations on parameter settings when using external databases like
Oracle with T24?
Answer

We recommend the below parameters to be set in the initialisation file [pfile/ spfile] to bring
about performance improvement -
parameters:
STATISTICS_LEVEL=TYPICAL
Sampled statistics are gathered automatically when STATISTICS_LEVEL is set to TYPICAL or
ALL. Normally, a value of TYPICAL is enough to gather statistics for all segments. You can
also set to 'ALL' but at the cost of additional I/O.
OPTIMIZER_INDEX_COST_ADJ=1
Ensure Optimizer will use available function base indexes for XML CLOB type. This results in
better utilisation of index, and thereby comes up with the fastest execution plan
FILESYSTEMIO_OPTIONS=SETALL
enable both direct I/O and asynch I/O
CURSOR_SHARING=SIMILAR
Oracle can allow similar statements to share SQL by replacing literals with system-
generated bind variables. Setting it to a value of SIMILAR can greatly benefit queries
coming from our T24 application.
Additionally,
OPEN_CURSORS=5000
Ensure sufficient handles for OCI statement caching
SESSION_CACHED_CURSORS=5000
Ensure cursors can also be cached
Note that the above settings should not be treated as fixed ones. Always consult your DBA
and refer to the release notes of the Direct connect driver that come along with your driver
for any changes / additions.

Question

How can I check the current jBASE license and the type of license used?

Answer

Use the command -

jInstallKey -v
Type 1 is ‘Standard edition’
Type 2 is ‘Enterprise edition’ - [includes Standard edition + TJ module]
Type 3 is ‘Non Stop edition’ - [includes Enterprise + resilience]
P.S -
The ‘Products’ code(s) in the output of jInstallKey are deliberately cryptic.

Question

Will an Account statement show the transactions that are reversed?

Answer

Depends on the type of transaction, the mechanism for production of account statement,
viz. delivery or enquiry and the day on which the reversal occurred. When reversed within
the same statement period, transactions like FT,TT update MASK.PRINT in STMT.ENTRY as
SYSTEM. Delivery based statements ignore reversed transactions. Enquiry based statements
do not ignore reversed transactions unless MASK.PRINT EQ '' is set as a fixed selection
criteria. Please refer to MB.ACCOUNT.STATEMENT for more details.

Question

How can we suppress the generation of account statement for internal account?

Answer

In order to suppress the generation of account statement for internal account completely,
you have to set the field PRINT.STMT in the ACCOUNT.STATEMENT application as 'NO'.

Question

From which applications can account balance figures like Monthly account balances, daily
account balances be fetched?

Answer

I. You can get this information from ACCT.ACTIVITY file which is a live file. It
updates online, shows the day wise daily credit and debit and closing balance.
II. You can use Enquiry STMT.ENT.BOOK or VAL.STMT.ENT.BOOK based on your
system. If it is a value-dated system then use VAL.STMT.ENT.BOOK, and if Trade
dated then you can use STMT.ENT.BOOK enquiry. These enquiries will give you
balance of accounts for different date criteria.

Question

Is there any parameter which can restrict the account to go into debit balance?

Answer

No, there is no parameter to restrict the account getting into debit balance, however if any
transaction tries to make balances of account to debit then an override ‘Unauthorised
overdraft’ will be generated by the system. If you wish to stop such kind of transaction you
can make use of Dispo officer setup / Overrides to restrict users to authorise transactions
with such override. Please refer to the “How to” link for the setup.

Question

Can the accounts category be amended? What are the implications?

Answer

Yes, accounts category can be changed. Following are the implications of changing the
category: I) Condition group of Account will change based on new category. II) Change in
CONDITION.GROUP will affect the Cr & Dr interest rate. III) Consol key of account may
change based on new category. IV) Balance in old CAL will be moved to new CAL.

Question
What are the steps to change the length of ALT.ACCT.ID field in Account Application?

Answer

Field ALT.ACCT.TYPE & ALT.ACCT.ID are associated multi value sets. The length of each
multi value set can be defined uniquely through the application ALT.ACCT.PARAMETER. Only
the length is unique and other parameters like masking field type goes by the first multi
value set.

Question

Is it possible to de-link accounts from one customer and attach to a new customer?

Answer

No, you can’t de-link accounts from customer. Perhaps you can close this account and
create a new one for required customer. However, one exception to this rule is if the new
customer is an existing joint Holder for the account.

Question

How to generate MT940 or MT941 instead of default MT950 statement?

Answer

You have to manually specify either 940 or 940 as per your requirement in the field
SWIFT.STMT.TYPE of the application ACCOUNT.STATEMENT.

Question

Can STMT.ENT.BOOK enquiry be used to check account balances?

Answer

No, if you are in a value dated system, you should not use STMT.ENT.BOOK enquiry to
check account balances, this is only for trade dated system. Use VAL.STMT.ENT.BOOK
enquiry instead.

Question

When will the account be marked inactive and how to mark it as active?

Answer

Marking an Account Inactive: =========================== In the Company

record there is a field called INACTIVITY.MONTHS. It indicates the number of months
without customer activity before an account is declared as inactive. And inside the account
record the inactivity is marked by INACTIV.MARKER field. This marker is set whenever the
dates of the last credit and debit entries generated by the Customer (Last Credit Customer
and Last Debit Customer fields) are more than x months ago, where x is the number of
months specified in the Company record in the field, INACTIVITY.MONTHS. When this
marker is set, no entries will be accepted without an override. This marker is set during the
end of day processing by the job, IC.UPDATE.INACTIVE in MARK.ACCOUNTS.INACTIVE
batch. The job, IC.UPDATE.INACTIVE.POST in the same batch updates the INACTIVE
ACCOUNTS in ACCOUNT.INACTIVE file. Resetting Inactive Marker:
========================== An inactive account can only be reset by running
a special Account Inactive Reset program through the Application, ACCT.INACTIVE.RESET.
The field, RESET.DATE in this record determines the date from which an inactive Account
will be made active. Once this record is authorised the INACTIV.MARKER field in the Account
record is automatically removed.

Question

If one account is never debited over one year, but gets credited, Does it become DORMANT
(inactive) account?

Answer

Accounts are made inactive when there are no transactions occurring for a particular
number of months as set in the field INACTIVITY.MONTHS in the COMPANY application.

Once the time duration specified in the COMPANY application is crossed without a single
transaction in an account, the field named INACTIV.MARKER... in that particular account
record will be set to Y, which indicates this ACCOUNT is inactive for further use. Further
transactions done on such accounts will generate override saying account inactive.
In your case, since there are CREDIT transactions, the account will not be INACTIVE and it
cannot be a Dormant account.

Inactive accounts will be determined only by Customer initiated transactions, and presence
of system initiated transactions like interest accruals, etc. will not be counted to determine
if an account is inactive.

Question

How can I set up a flat monthly account maintenance charge in T24 (the charge is a flat
amount charged independently of the balance of the account)?

Answer

Calculation of flat charges for an account independent of account balance can be achieved
through IC.CHARGE application setup.

Question

How does the system work during both COB and online, if the customer/account has a
POSTING.RESTRICT?

Answer

If the customer/account has a restriction, the system will raise an override during online
processing which the user has to accept to commit.
In case of interest entries (debit interest, charges etc) generated in the COB, system will
automatically accept the override and the generated override will be stored in the
corresponding entry.

Question

The enquiry, VAL.STMT.ENT.BOOK gets entry details from the file STMT.VAL.ENTRY and due
to performance problem this concat file updates was restricted for internal accounts.

Answer

The enquiry, VAL.STMT.ENT.BOOK gets entry details from the file STMT.VAL.ENTRY and due
to performance problem this concat file updates was restricted for internal accounts.

In case you want this enquiry to work for internal accounts then you have to build the
STMT.VAL.ENTRY by following the procedure as follows:
1. Run BUILD.STMT.VAL.ENTRY as a mainline program from Globus prompt. This can be
done either soon after EOD or just before EOD. Type "Y" when prompted, "DO YOU WANT
TO RUN THIS APPLICATION?"
This will clear the file STMT.VAL.ENTRY and rebuild the file for all accounts.
2. We have an Adhoc job EOD.BLD.STMT.VAL.ENT in the batch FILE.TIDY.UP. This job
will build STMT.VAL.ENTRY for internal accounts based on the entries generated on that day.
Change the frequency of this job to Daily.
3. To avoid performance issues, consolidate the entries for internal accounts.
4. Set the field VAL.NO.MONTHS in ACCOUNT.PARAMETER, used to define the number
of months that value dated information is to be retained on the system. STMT.ENTRY
identifiers are held on STMT.VAL.ENTRY by account number and value date. The job
PURGE.STMT.VAL.ENTRY uses the number of months defined here to calculate a date from
today before which STMT.VAL.ENTRY records will be removed. This is also an Adhoc job.
5. HUGE volume of transactions in STMT.VAL.ENTRY leads to performance thread,
hence kindly purge STMT.VAL.ENTRY at a frequency of once in 6 months.

Note: Test the procedure before implementing it on the LIVE system and this process of
rebuild may take a considerably longer time depending upon the volume of entries.

Question

Why cannot master account be given as the settlement account to close the sub-account? Is
there a provision to acheive this functionality?

Answer

Currently this functionality (giving master account as a settlement account) is not available
in core; this has to be done locally.
Write a routine to remove the sub-account from AC.SUB.ACCOUNT and attach this in the
account closure version as an input routine and using this version close the account.

Question

What is the use of the field ENT.UPDATE.TODAY in ACCOUNT.PARAMETER?

Answer

In ACCOUNT.PARAMETER, setting the field ENT.TODAY.UPDATE to NO will not update any of

the TODAY files i.e. ACCT.ENT.TODAY, CATEG.ENT.TODAY & RE.SPEC.ENT.TODAY. If the
TODAY files are not populated then the LWORK.DAY files will also be blank.
Currently there are many modules using TODAY and LWORK.DAY files, hence this setup is
not recommended.

Question

Why does the system display an override ‘Overdraft on available balance’ for accounts with
available funds even after upgrading to higher release?

Answer

In most of the cases this override is often seen after an upgrade. For this, we generally
advice to run the REBUILD.AVAIL.FUNDS job. This job has an adhoc frequency which has to
be changed to daily frequency and run in the first COB after upgrade. This job uses the
AF.REBUILD.REQUEST application. This application has the account numbers for which the
job has to rebuild the available ladder.

Question

How to archive the STMT.ENTRY completely?

Answer

As per existing functionality, archiving will be performed based on the ACCT.STMT.PRINT

record.
1. If the ACCT.STMT.PRINT for an account has less than 2 multi-value sets, then the entries
for that account record will not be archived.
2. Also if the entries yet to be printed (i.e. present in AC.STMT.HANDOFF) exist within the
Purge date defined, it will not get archived.

Question

Can the value of CASH.FLOW.DAYS be changed in the midst of a live T24 System? In that
case what will be the effect?

Answer

Yes. The value of CASH.FLOW.DAYS can be changed in a T24 live System. The change will
not get effected for accounts already having the ladder; only for newer transactions does it
get affected

Question

Is there a table that contains all the movements of the STMT.ENTRY for a certain day?

Answer
The transaction while authorised, will generate the STMT.ENTRY. Some of the concat files
below will hold the STMT.ENTRY ids.
i) ACCT.ENT.TODAY : For transaction that are processed today.
ii) STMT.PRINTED : For transaction that falls under specified statement period specified
in the ACCOUNT.STATEMENT's STMT.FQU.1field.STMT.ENTRY ID in ACCT.ENT.TODAY will
also be present in STMT.PRINTED.
iii)ACCT.ENT.LWORK.DAY : For transaction that were processed in the previous working
day.
iv)ACCT.ENT.FWD : For future dated transaction.
The above concat files will contain the STMT.ENTRY IDs and can be made use to extract the
list of transactions to build the flat file needed.

Question

Why are the entries not posted to the sub-account even after defining the sub-account set-
up to prevent locking in the master account?

Answer

Setting the MAX.SUB.ACCOUNT field to a value greater than ‘1’ in the master account would
prevent this problem. After setting the MAX.SUB.ACCOUNT greater than 2, on further
transactions system will post the transaction to the sub account.

Question

When should a file be distributed?

Answer

Certain releases of Jbase on 32-bit systems have a restriction on the size of the file to be
not greater than 2 GB. As a file's size approaches 2 GB, the tendency for file instability
increases. Our recommendation is to keep the files below 2 GB with regular archiving.
However, if distribution is still required due to volumes, please get in touch with
cshd@temenos.com for automatic procedure.

Question

During COB, one of the local job crashes out in EOD.ACCOUNTING with the message “Array
index out of bound”. How to fix this problem?

Answer

The problem is because the common variable, V is not initialised before calling
EB.ACCOUNTING. Variable V must be set with the field number of AUDIT.DATE.TIME of the
relevant application before calling EB.ACCOUNTING. Log an issue with PACS if it is a core
job.

Question

Why does the system display duplicate Till accounts while executing the enquiry
TELLER.POSITION?
Answer

System will display all the Internal Accounts across all the companies while executing the
TELLER.POSITION enquiry and that is reason you find duplicate Till accounts. While
launching the ENQUIRY, there is a SELECTION.FIELD by name SHOW.TILL.ACS which is
used to filter the Internal A/C s of the particular category and opting this will avoid duplicate
display of TILL ids.

Question

Why is intercompany transaction possible through Funds Transfer but not through Data
Capture?

Answer

As per the current functionality the intercompany transaction for Data Capture is not
possible. Data Capture can be used to pass adjustment entries for that particular company
only. The intercompany transaction is possible through Funds Transfer and Teller but is not
possible through Data Capture. System will raise the error "ACCOUNT NOT IN THIS
COMPANY" when account form another company is input in DC transaction.

Question

Why does the system raise the error "EB.RTN.NO.GRP.CALCULATED - Condition Id =

"FUNDS.TRANSFER" when creating a New Customer or New Account in a newly installed
area?

Answer

In this case the CONDITION.PRIORITY records are created but the relevant
XX.GEN.CONDITION and XX.GROUP.CONDTION (where XX is the application like FT for
FUNDS.TRANSFER) are not created. In order to resolve the problem kindly create the
respective XX.GEN.CONDITION and XX.GROUP.CONDITION. Please refer to the User Guide
and Help Text related to CONDITION.PRIORITY for further reference.

Question

Is it possible to have different customised backgrounds per Branch (in a Multi Book set up)
or per Company (in a Multi Company set up)?

Answer

As per the current functionality of T24, we could attach only one skin for a USER record and
the defined skin will be reflected in all the Company records which are defined in the
corresponding USER record. As per the current T24 Browser functionality, a Browser skin
can be attached only to a specific user and not to the different company's of the same
USER.

Question
How to improve select performance on I-type fields which extracts contiguous string from
another field?

Answer

We recommend to replace I-type whereever possible. I-types of the below form -

jsh pb ~ -->CT DICT FBNK.LMM.HISTORY.LIST CONT.ID.ARC
001 I
002 @ID[1,12]
003
004 CONT.ID.ARC
005 12L
006 S
007
008
009
010
011
012
013
014 @ID[1,12]
can be re-written to -
CONT.ID.ARC.NEW
001 D
002 0
003 F;0;C1;C12;[]
004 CONT.ID.ARC.NEW
005 12L
006 S
where:
0 = Attribute zero (RECID)
C1 = Start position of substring extraction
C12 = End position of substring extraction
for performance benefit.

Question

How to set up "Trade Date accounting" and “Value Date Accounting" in T24?

Answer

The option of Trade Dated System or Value Dated System can be set in the
ACCOUNT.PARAMETER table using the field VALUE.DATED.ACCTNG.
For Trade Dated System, set this field as 'N' or 'NO' and for Value Dated System set this
field to 'Y'.
By functionality we can convert system from Trade Dated to Value Dated but not vice versa.

Question

Why is the following error message “field already store concatfile: &6” displayed while trying
to authorise an internal account?
Answer

The mnemonic field in an account record can be used as an alternative method of

referencing the account. Therefore the Mnemonics must be unique. In order to attain this,
T24 maintains a separate concat file called MNEMONIC.ACCOUNT where the account IDs are
stored and is updated with MNEMONIC as ID containing the Account number as field content
as shown below:
BNK MODEL BANK MNEMONIC.ACCOUNT SEE
MNEMONIC.......... EUROCJPY
------------------------------------------------------------------------------
1 ACCOUNT........... 26816 EUROCLEAR

------------------------------------------------------------------------------
26 AUG 2009 18:39:24 USER (09 DEC) SUNITHA2 [11001,6PAGE 1
ACTION
AWAITING PAGE INSTRUCTIONS
So, when we try to give an already existing Mnemonic for a new Account, system will
automatically throw the reported error which is the current design of T24. Perhaps the error
can be avoided by giving a different value in the Mnemonic field.

Question

How to reverse ADI/ACI?

Answer

Reversal of ADI/ACI record is not possible. If you want the system to refer the
corresponding GDI/GCI record (that is effective for that capitalisation period) instead of
ADI/ACI record then input GENERAL in the field INTEREST.DAY.BASIS in the ADI/ACI
record.

Question

How to setup flat daily charges for an account/group of account?

Answer

Flat daily charges can be set for an account/group of accounts using the application
IC.CHARGE
IC.CHARGE set for the account 10049:
R8 MODEL BANK IC.CHARGE SEE
IC.CHARGE.ID...... A-10049
------------------------------------------------------------------------------
1. 1 IC.CHG.PRODUCT. TEST FOR GEN CHG TEST
2. 1 CAL.STEP.PERIOD P
3. 1 CHRG.FREQUENCY. 20100211DAILY 11 FEB 2010 Daily
4. 1 CHRG.EFF.DATE.. 11 FEB 2010
19 CURR.NO........... 1
20. 1 INPUTTER....... 4_AUTHORISER
21. 1 DATE.TIME...... 16 JUL 09 11:36
 22 AUTHORISER........ 4_AUTHORISER
23 CO.CODE........... GB-001-0001 R8 MODEL BANK
24 DEPT.CODE......... 1
------------------------------------------------------------------------------
16 JUL 2009 11:37:11 USER (11 FEB) AUTHORISER [4,IN] PAGE 1
ACTION
AWAITING PAGE INSTRUCTIONS
IC.CHARGE set for all the accounts in the group '1':
R8 MODEL BANK IC.CHARGE SEE
IC.CHARGE.ID...... G-1
------------------------------------------------------------------------------
1. 1 IC.CHG.PRODUCT. TEST FOR GEN CHG TEST
2. 1 CAL.STEP.PERIOD P
3. 1 CHRG.FREQUENCY. 20100211DAILY 11 FEB 2010 Daily
4. 1 CHRG.EFF.DATE.. 11 FEB 2010
19 CURR.NO........... 1
20. 1 INPUTTER....... 4_AUTHORISER
21. 1 DATE.TIME...... 16 JUL 09 11:36
22 AUTHORISER........ 4_AUTHORISER
23 CO.CODE........... GB-001-0001 R8 MODEL BANK
24 DEPT.CODE......... 1
------------------------------------------------------------------------------
16 JUL 2009 11:38:09 USER (11 FEB) AUTHORISER [4,IN] PAGE 1
ACTION
AWAITING PAGE INSTRUCTIONS

Question

Can I setup IC.CHARGE for group of accounts with particular currency?

Answer

Yes, charges can be setup for a group of accounts with particular currency as given below
R8 MODEL BANK IC.CHARGE SEE
IC.CHARGE.ID...... G-1
------------------------------------------------------------------------------
1. 1 IC.CHG.PRODUCT. TEST FOR GEN CHG TEST
2. 1 CAL.STEP.PERIOD P
3. 1 CHRG.FREQUENCY. 20100211DAILY 11 FEB 2010 Daily
4. 1 CHRG.EFF.DATE.. 11 FEB 2010
19 CURR.NO........... 1
20. 1 INPUTTER....... 4_AUTHORISER
21. 1 DATE.TIME...... 16 JUL 09 11:36
22 AUTHORISER........ 4_AUTHORISER
23 CO.CODE........... GB-001-0001 R8 MODEL BANK
24 DEPT.CODE......... 1
------------------------------------------------------------------------------
16 JUL 2009 11:38:09 USER (11 FEB) AUTHORISER [4,IN] PAGE 1
ACTION
AWAITING PAGE INSTRUCTIONS

Question
 How to improve select performance on I-type fields which extracts contiguous string from
another field?

Answer

Use 'G' correlative . I-type dictionaries are always a performance hit and hence should be
avoided wherever possible. For e.g. the dictionary of the table FBNK.TXN.JOURNAL contains
several fields which extract a string from the @ID - COMPANY.CODE, PROCESS.DATE,
APPLICATION.ID and CONTINGENT.IND. These fields can be changed like below -
from:
PROCESS.DATE
001 I
002 @ID["*",3,1]
003
004 PROCESS.DATE
005 8R
006 S
007
008
009
010
011
012
013
014 @ID["*",3,1]
to:
MY.PROCESS.DATE
001 D
002 0
003 G2*1
004 MY.PROCESS.DATE
005 8R
006 S
This should give significant performance improvement.
Some notes on G Conversion:
---------------------------
G codes extract one or more contiguous strings (separated by a specified character), from a
field value.

SYNTAX
G{m}xn

SYNTAX ELEMENTS
m is the number of strings to skip. If omitted or zero, extraction begins with the first
character.
x is the separation character.
n is the number of strings to be extracted.
NOTES
The field value can consist of any number of strings, each separated by the specified
character. The separator can be any non-numeric character, except a system delimiter.
If m is zero or null and the separator x is not found, the whole field will be returned. If m is
not zero or null and the separator x is not found, null will be returned.
INPUT CONVERSION
Input conversion does not invert. It simply applies the group extraction to the input data.
EXAMPLE 1
G0.1
If the field contains "123.45", 123 will be returned. You could also use "G.1" to achieve the
same effect.
EXAMPLE 2
G2/1
If the field contains "ABC/DEF/GHI", GHI will be returned.
EXAMPLE 3
G0,3
If the field contains "ABC,DEF,GHI,JKL", ABC,DEF,GHI will be returned. Note that the field
separators are included in the returned string.

Question

Is there an easy way to get the routine flow without going in to debugger?

Answer

Use:
CRT OCONV('','U0016')
in the final routine [or redirect to a variable]. This should give the routine flow.

Question

Why are the agents not exiting after COB? The process listing collected using 'ps' command
shows them as <defunct>.

Answer

You must be in a release pre-jBASE 5.0.13 [where this issue is fixed]. The below
environment variable should be used to avoid this issue -
export JBASE_DISABLE_NEW_PHANTOM=1
NOTE -
Mostly the loginproc used for entering in to T24/ jshell is as below -

0001 PQN
0002 OSTART GLOBUS Y/N
0003 IP%1
0004 IF %1 # "Y" IF %1 # "y" GO 99
0005 HEBS.TERMINAL.SELECT
0006 P
0007 HEX
0008 P
0009 99 Hjsh -s jsh
0010 PX
In a para, 'P' is to continue to next command while an 'X' forces an exit. Often, line after the
call to EX is a 'P' rather than a required 'PX'. This 'X' ensures a proper exit from the server
when you exit from T24 [rather than chaining to the next command].
So, the loginproc should be -
0004 IF %1 # "Y" IF %1 # "y" GO 99
0005 HEBS.TERMINAL.SELECT
0006 P
0007 HEX
0008 PX

Question

Will there be any impact when changing the category of an account from normal savings to
staff savings?

Answer

The result of changing the category will be a change in account group (consol key). But this
change will not happen online and will happen only during COB. There will be no impact
because the account will be removed from the old link file and added to the new consol key
and the CAL balance changes accordingly.

Question

What should I do if I see "ORA-01555: snapshot too old" messages in driver log?

Answer

The Oracle server guarantees that a statement sees data from a consistent time, even if the
data is modified by other transactions. Consider the case where a long running query is
executed at a time when several database updates are being made. If a row has changed
[due to the other db updates] that were not committed at the start of the query [SELECT],
then ideally the SELECT should process the old data and not the one that are committed at
the time of execution of this query. Oracle does this by constructing a read-consistent
image of the row by retrieving the before image of the changes from the undo segment and
then applying the changes to a copy of the row in memory. An Undo table space is used to
store undo data. What happens if the required undo data cannot be found? You will get this
error.
Recommendations and suggestions to prevent this error:
1. Set the UNDO_MANAGEMENT parameter to AUTO in the initialisation parameter file to
enable automatic undo management. Automatic undo management ensures automatic
creation, allocation and tuning of undo segments.
2. Check RETENTION value -
The value of the UNDO_RETENTION parameter sets the duration, in seconds, to preserve
committed information in the undo segments. Check the output of below queries -
a) Issue due to low retention value
SQL> show parameter undo_retention;
The default value for UNDO_RETENTION is 900 seconds (15 minutes), is never sufficient for
T24 operations. The recommended initial UNDO_RETENTION setting is 10800 (3 hours).
This should be monitored and increased if necessary. Some sites are running with 14400 (4
hours), 18000 (5 hours) etc.
b) Issue due to PCTVERSION being used
SQL> select pctversion, retention from user_lobs where table_name = ‘table name’;
We need to know the pctversion value because of the below bug [pre-Oracle 10.2.0.4] –
Bug 5176017 - Exp/imp loses "RETENTION" settings of LOB columns
If a table with a LOB is created using a RETENTION setting, export does not retain this
setting and changes the flag to PCTVERSION. This problem is fixed in Oracle 10.2.0.4 patch
set 3.
ie, the UNDO_RETENTION parameter may NOT be referred always - depends upon whether
PCTVERSION is set in your database. Undo segment could be space based on a
PCTVERSION and the default value is 10%. This might just prove to be insufficient for the
number of writes happening in a second. [ie. the tables will not use undo_retention if
PCTVERSION is set which we may be unaware of. And the default value is only 10% which
is very low]. So, check whether pctversion is used using the above query.
3. Forcing required retention on a table
Use the below DDL -
alter table <table name> modify lob (column_name) (retention);
where COLUMN_NAME can be obtained from the output of dba_lobs for the corresponding
table.
If problem persists, report it to helpdesk immediately.

Question

Can we use Apache Tomcat as web server for a T24 installation or does R9 requires
additional features that are not supported by Apache Tomcat?

Answer

From R09 onwards the remote JCA (Java Connection Agent) is the default connection
method to T24. It is an industry standard, JEE compliant, connection that is capable of
leveraging all the proprietary features of high end applications servers such as Websphere.
All functionality previously available from the TC connection mechanism will be available in
this fast, resilient, and scalable architecture. See Browser Installation and Configuration for
more details.
The JCA connection method can ONLY be utilised when T24 Browser/ARC-IB is installed on
an Application Server such as JBoss. JCA will NOT function under a simple web server such
as TomCat.
Tomcat vs. JBoss is not generally relevant to the discussion as Tomcat is used inside JBoss
as the servlet runner. The JCA requires an application server e.g. JBoss, Websphere or
Weblogic.

Question

Why is the Validation routine not triggered when OFS is used?

Answer

Set FIELD.VAL field of the OFS.SOURCE record to YES.

Question
Why is the F.OFS.MESSAGE.QUEUE not getting populated when we are calling a mainline
routine?

Answer

When you are calling OFS.POST.MESSAGE from a mainline routine, you should call
JOURNAL.UPDATE also.
We also request you to call the JOURNAL.UPDATE for each message separately in the
MAINLINE routine to avoid running out of cache problem.
Note: When OFS.POST.MESSAGE is called from the version routine then there is no need to
call JOURNAL.UPDATE it will be handled by Core TEMPLATE.

Question

The F.OFS.REQUEST.DETAIL file size is huge in size and increasing rapidly. What can we do
for that?

Answer

You can stop writing the OFS.REQUEST.DETAIL by nullifying the field MAINT.MSG.DETS in
the corresponding OFS.SOURCE record.
You can also delete the records manually -
It won’t make any financial impact. This file is maintained as LOG details for the OFS
processing.

Question

Is it possible to reinstall a patch? Is it a valid process to do?

Answer

It is possible to reinstall a patch and it is a valid process. But, all the dependent patches for
a patch should be reinstalled again before reinstalling the patch. We strongly advise not to
reinstall a patch, unless there is a genuine need for it.
Note: Duplication of Patch names will be noticed in the SPF record.

Question

Is it possible to remove an installed patch?

Answer

It is not possible to remove a patch that is installed in an environment. The alternate

solution is to restore T24 libraries (globuslib/t24lib) and T24 binaries (globusbin/t24bin)
from recent backup and to reinstall all the necessary patches that are installed after the
backup is taken.

Question
During Upgrade the Why is the enquiry CUSTOMER.POSITION not displaying any records
during upgrade?

Answer

In earlier release of T24 say R05, the ID of the CUSTOMER.POSITION enquiry included the
Terminal Number. So, USER.REC used to pass the Terminal Number to the routine
E.USER.NO.
However in higher releases of T24, the I-descriptor USER.REC has been removed from
CUSTOMER.POSITION. Hence in your ENQUIRY record CUSTOMER.POSITION, kindly remove
the FIXED.SELECTION based on USER.REC (USER.REC EQ 1) and authorise the ENQUIRY
record CUSTOMER.POSITION.

Question

Can any network location be pointed to store the images uploaded (instead of a directory in
the web server)?

Answer

When images are captured through Browser, they get stored in the path specified in the
IM.IMAGE.TYPE application.

In Browser, if the Webserver is installed in the Windows machine, the captured image can
be stored in any of the folders of the default/network drive based on that parameter in the
IM.IMAGE.TYPE application. But, if the Webserver is installed in a non windows
environment, such as AIX, UNIX, etc, the captured image should be stored in a directory
created under the webapps/BrowserWeb directory. (In this case the Default Drive field in
the IM.IMAGE.TYPE application should be left blank).Do not input anything in the Default
Drive field.

Question

Can a scanner be used directly to scan a document into Browser instead of selecting a file
from a specific path?

Answer

No, we can only upload the images to T24 Browser by using IM.DOCUMENT.UPLOAD
application. By doing this, some JavaScript codes are involved in the Browser front end to
encrypt images for security reasons and will upload the same in the web server path
specified in the corresponding IM.IMAGE.TYPE application. Hence, please scan the
documents by using Scanners and save it in temporary files and upload the images using
IM.DOCUMENT.UPLOAD.