Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Home
About Us
Jobs
Disclaimer
Privacy Policy
Contact us
T24
T24
T24
T24
T24
T24
T24
T24
Basics
Interface
Functional
Technical
Programming
Tips & Tutorials
User Guides
News
Stage
Description of activities
APPLICATION
SYSTEM WIDE
REPORTING
START OF DAY
ON LINE
Any non critical reports and processes that can be run afte
the system has returned to on line mode.
The Close of Business runs various processes based on the order above, in order
of stages and within the stage based on the sequence number.
Each batch stage consists of a number of processes with the same or different
sequence number, which corresponds directly to records in the BATCH file, and
each process consists of a number of jobs for which routines are defined in the
PGM.FILE as type B. Each batch process defines the stage and sequence at
which it has to be run, the jobs to be run and the frequency in which it has to be
run.
At no point, the stage and the sequence of the batch process will be violated
thus ensuring data integrity and proper processing of jobs if they are dependent
on an earlier job.
Pre-requisites
In order to get the most out of this manual, it is essential that you are familiar
with the standard procedures regarding navigating your way around the system.
This includes items such as program access via menus, data entry and editing,
mandatory and multilevel fields, committing details, and so forth. All of these
are described in detail in the Navigation manual.
Multiple session Close of Business
T24 Close of Business processes have been designed to run as multi threaded to
reduce the time taken and to maximise the usage of system resources. Multiple
agents can be used to run the Close of Business and they share the job load.
However, this will not affect the sequence or the verification of the Close of
Business. The agents complement each other within the same stage and
sequence and do not violate the agents, thus ensuring data integrity.
The Manager only requires one agent (above) whereas 2 to 3 agents for the COB
are sufficient (below)
Step 2 TSA.PARAMETER
There is only one record SYSTEM. This application tells the Service Manager at
which levels (in seconds) to review and restart the Agents.
Note: The server name is not a mandatory field. The tSM obtains the server
name it should run, by executing the hostname command. It then tries to match
that with the value entered in the field SERVER.NAME in TSA.SERVICE of
the agent. If it does not match then it could not start the agents. If there is no
value in the field SERVER.NAME, the tSM uses the value captured by it (through
the hostname command). So there is no need for the SERVER.NAME field in
TSA.SERVICE. This applies both to local host as well as server.
Note: The server name is not a mandatory field. The tSM obtains the server
name it should run, by executing the hostname command. It then tries to match
that with the value entered in the field SERVER.NAME in TSA.SERVICE of the
agent. If it does not match then it could not start the agents. If there is no value
in the field SERVER.NAME, the tSM uses the value captured by it (through the
hostname command). So there is no need for the SERVER.NAME field in
TSA.SERVICE. This applies both to local host as well as server.
To invoke Close of Business
As Agents may become stuck, we recommend that you first STOP all Agents,
and then clear the table F.TSA.STATUS at the j prompt as follows:
> CLEAR.FILE F.TSA.STATUS
Also clear the EB.EOD.ERROR file once the errors occurred during the Close of
Business have been fixed, by entering F.EB.EOD.ERROR at the j-prompts as
follows:
> CLEAR.FILE F.EB.EOD.ERROR
Agent 2 has been started and the COB is underway, now start Agent 3:
Example of processing screens (with COMO as Agents were started with DEBUG
statement)
Step 3
When the COB is completed, the Service Manager automatically stops the
Agents this is the display:
Step 4
Return to the TSA.SERVICE, application and STOP the TSM record. You will note
that the status of COB is already set to STOP.
List Files
Every job during the Close of Business uses a LIST file for storing and sharing
records for processing between different agents. The LIST file is dynamically
determined based on the session number doing the SELECT processing of a
multi threaded job. The other agents use the allotted list for sharing their load of
the job. The LIST file is empty at the end of the job thus making it available for a
different job.
COMO
Since the introduction of multi threaded architecture, the COMO is written with
the session number to distinguish processing between different threads.
The COMO is written with the key as TSA_<agent no>_datetime.
It is recommended that all COB COMOs be retained securely for at least six
weeks.
If there is an occasion to restore and rerun, then the COMOs should be printed or
copied to a secure medium before the restore takes place.
Example of the COMO with an error:
Monitoring COB
Three enquiries are available that assist the monitoring the progress of Close of
Business and the records processed with the time taken. They can be accessed
via the Temenos Enterprise Console.
COB.PROGRESS A listing of active companies and an indication (progress bar)
of their time to completion.
JOB.PROGRESS This enquiry list all active and completed jobs by descending
start times (i.e. current on top). It shows the start time, end time, elapsed time,
contracts processed, total contracts to process, throughput (contracts/minute)
and individual server rate. The latter is the number of contracts processed in
one minute by a server process this will be compared historically to see if the
job is slowing down as time passes.
JOB.HISTORY Drilling down from the JOB.PROGRESS, the user can see a graph
of the elapsed time of the last ten runs of the job and the individual server rate.
If the latter figure rises over time; it indicates a problem, which could be badly
sized files.
Batch Output
All reports, COMOs, etc. produced by the batch system are output using the T24
Report Control system. This enables the operator to determine the destination
printer, user addressing, number of copies, etc.
The following applications are used in this process:
Application
Description
SPOOL.BATCH.OUTPUT
SPF
HOLD.CONTROL
PRINTER.ID
USER
In order to access the reports generated during the Close of Business, follow
these steps:
Access
Enter ENQ REPORT.LIST in the Command Line.
Procedure
1.
2.
3.
4.
Screen
A screen like the one shown below displays, allowing you to filter the records for
on screen enquiry or report.
Selection criteria may include part of a report name, or not entering any
selection criteria, the system displays all reports generated and held as per the
number of days defined in the SPF record.
When the enquiry displays, it will appear like the screen shown below.
Select the report by clicking on the View Report ID against the record displayed
in the report list.
Error Handling
Error Message
Problem
ILLEGAL ORDER
INITIALISES ERROR
JOB ERROR
NO ENTRY IN PGM.FILE
REC MISSING
RESTORE DB
Data Capture
Latest Posts
T24 Data Migration for Customer and Address - November 29, 2016
Metro Bank launches new online platform with Backbase - November 24,
2016
Vancity CU goes live on Temenos T24 core banking system - November 24,
2016
View All Posts
Post navigation
Why ASSET PROVISIONING Needed?
T24 TSA Service
One comment
Yoshan
Very useful article for the all the T24 Operation guys.
Reply
Leave a Reply
Your email address will not be published. Required fields are marked *
Comment
Name *
Email *
Website
Post Comment
Our Visitors
5,306 Pageviews
Dec. 01st - Dec. 31st
Home
About Us
Jobs
Disclaimer
Privacy Policy
Contact us