Intr t24
Intr t24
enquiry reports=Enquiry reports can be saved in various format. Can you print an
enquiry report from T24?
The applications to be set are ENQUIRY.REPORT , REPORT.CONTROL, DE.FORM.TYPE and
PRINTER.ID
PRINTER.ID is the application used to define the valid printers on the system
Any report printed from your T24 system should have an entry in REPORT.CONTROL
application
REPORT.CONTROL holds the description of the report, the printer environment (form),
the date and time last produced and spooled
When the enquiry report is printed using the print to server option, your report is
spooled in the &HOLD& director
---------------------------------------------------------------
AUTO.NEW CONENT RTN:: They can be used to manipulate the content of the field
before display
They get executed after the id of the record is supplied by the user and the
corresponding record is fetched from the file, but before the record can be
displayed
TXTINP(EB.DISPLAY.WORKFLOW)
ID.RTN( TO MANIPULATE ID OF THE RECORD)
AUTO.NEW.CONTENT
CHEK.REC.RTN
VALIDATION.RTN
INPUT.RTN
AFTR.UNAUTH
BEFORE.AUTH
AUTH
-----------------------------------------------------------
� When a single process can be executed by more than one processor, the process
is said to be multi-threaded
MULTITHREAD==
create a total of 4 components for every multi threaded routine in T24.
I_COMMON, .LOAD,.SELECT(BATCH.BUILD.LIST PREPARES THE LIST FILE), .PROCESS OR
RECORD
TO EXCUTE THESE 4 COMPONENT
A tSA (T24 Service Agent) is a program that eventually calls BATCH.JOB.CONTROL.
This multi-threaded routine can either be run as a Service or as a COB Job.
BATCH.JOB.CONTROL -
***********Splits the job into �multiple� threads
Executes them simultaneously
Thus making optimum use of the available processors
------------
In case of a single threaded routine, there would be just one routine that would
have the logic of .LOAD, .SELECT and execution built into it.
Therefore, only 1 tSA would process the whole routine. However, in case of a multi
threaded routine,
the logic is split and written in the 3 separate routines, and multiple tSA�s can
execute it at the same time,
thereby decreasing the total time taken to execute a routine, and increasing
throughput.
--------------------------------
------------------
COB:: Close Of Business is used for processing events, calculating and posting
interest,
rolling the bank date forward and productions of various reports.
STAGES::=application wide:-individual application process(forex, ft)
system wide::-system wide process(interest, charges, revaulation etc)
reporting::-main system reports(general ledger,transaction journals)
start.of date(change date ex:changing ordders, split month end evets, cash flow
maintenance)
oline--any non critical reports and processes which can be run after the system
has return to on-linemode.
COMO will contain information on the jobs processed with the complete run time
information.
-------------
MONITORING COB::: 3 ENQUIRIES
1) COB.PROGRESS
2)JOB.PROGRESS
3) JOB.HISTORY
ERRO( EB.EOD.ERROR, EB.EOD.ERROR.DETAIL)
------------------------------------------------
TEMPLATE::
--------------
3)An application in T24 allows input of data and performs some business processing
too.
2)A collection of applications that work together to create business functionality
is called a PRODUCT.
For example, the Loan and Deposits product is made up a number of applications
that work together
There are different kinds of applications in T24
H type
U type
L type
T type
W type
The FILE.CONTROL record for each application contains the file classification of
the application (CUS, FIN, INT etc.)
This information is useful in deciding the naming convention that T24 will use for
the applications� files at database level.
INT (Installation):This group covers files like SECTOR, PGM.FILE, FILE.CONTROL etc
where only version of the file will exist regardless of the number of companies.
These files will be stored at the Head Office and will be accessed by all the
branches.
CUS (Customer):This group covers files like CUSTOMER. Usually these files exist in
the HO and
will have the bank mnemonic as the prefix. They are shared among all the branches.
Alternatively, these files can be stored at each of the branches as well.
If maintained at each of the branches, they cannot be shared. These files primarily
contain static information.
FIN (Financial):This group covers files like ACCOUNT, LD.LOANS.AND.DEPOSITS etc
where each
of the branches contain a copy of the file but do not share with the rest of the
bank.
--------------
THE template..
.initialise
.fields->fucntion-->id-->record-->validate-->preview->overrides-->process-
>validate->authorise-->run
-------------------------------------------------->
design studio(design studio provides developers with an eclipse based integrated
development environment.
it provide dedicated tool for each category of source artifct in core t24
including:::screns custom entry fields local code
--------------------
As a develpers configure chqnges, design studio genrates xml files under the cover,
tose files can be tracked throughout the design test deoploy process.scm
packager
To deploy a set of model files, they must be packaged using the packager and
installed into a T24 area using the installer.
Select Design Studio > Design Studio Template Project .
The New Design Template Projects dialog box is displayed.
Select from the drop down list the template t24-packager-tafj
Set Template parameters values.(project name, release tfjhome dir eetc) aftr
importing all data files n routines
.
Right click Launch T24 Packager from ftmodelbank-packager and select Run as Launch
T24 Packager(TAFJ)