5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 1/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 2/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 3/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 4/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 5/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 6/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 7/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

Each multi threaded routine in T24 must have a PGM.FILE entry with TYPE = B which
stands for BATCH.

Each B type routine has an entry in the BATCH application, and a service is no
different. A service could be made up of one multi threaded routine or multiple routines
that must be run in an order. You will use the BATCH record to define this order using
the JOB field. The BATCH record that you will create will NOT have a BATCH.STAGE
defined as this record must NOT be picked up during COB.

Finally, you must create a record in the application TSA.SERVICE. The ID of the
record must match the BATCH record Id. Why is this?  – This is because when you
start off a service, T24 looks for a record in the BATCH application and then finds out
which routine it must execute in the background.

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 8/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

In this example, an existing service called BNK/SWIFT.OUT is used. The screen shots
above show the identical TSA.SERVICE and BATCH record Ids.

From the BATCH record, you can find out the actual name of the multi threaded
routine and check it’s PGM.FILE entry
1. It is important to understand - Why the Bank Mnemonic is part of the BATCH
record ID?
This is because all processes are company specific. If we want the same process
to be executed for each company defined in the COMPANY application then we
have to have processes defined for every company separately.

For Example:
 A company with mnemonic BNK might want a process to run during COB whereas

another company
during COB. with way
The only mnemonic EU1
to do this in might
T24, isnot
to want the
create same process
a process to run
in the BATCH
application with ID prefixed with the mnemonic BNK and not EU1.
BNK/<Batch Process ID Name>

If you want this batch process to be executed for both BNK and EU1, then you
need to do the following. Create the following records in the BATCH application
BNK/<Batch Process ID Name>
EU1/<Batch Process ID Name>

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 9/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 10/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

1. BATCH.ENVIRONMENT
Defines the environment to run the process in, i.e foreground or background
 A foreground process will be run directly on the users terminal, whereas a background
process will run as a phantom task. The background facility allows the user to run a
number of processes concurrently.</p>

2. Job Name Contains the name of the routine to be executed. All routines defined
here will have an entry in PGM.FILE with TYPE set to ‘B’

3. Frequency specifies the frequency at which the batch job has to be executed. It can
have values as follows.
D specifies that the job will be executed every working day.
D nn specifies that the job will be executed every nnth working day
W specifies that the job will be executed on a weekly basis, that is every Friday
M specifies that the job will be executed on the last working day of every month
M nn specifies that the job will be executed every nn day of the month or previous
working day of each month
Y specifies that the job will be executed last working day of the year 
Y nn specifies that the job will be executed the last working day of the nn'th month
 A specifies that the job will be executed on an adhoc basis. You should manually
specify a date on which the job has to be executed.

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 11/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

1. In the field Verification, you can enter the name of the job (routine) which needs
to have been executed successfully on that day before the current job is executed .
For e.g. The job FT.PROCESS.BULK.PAYMENT will be executed only if the job
FT.PROCESS.BULK.PAYMENT.PRE has been executed successfully.
NOTE: Only jobs already defined in the current record can be entered in the field
Verification. Jobs belonging to other Processes (Batch Records) cannot be
entered in this field.
2. Next Run Date contains the date when the current job has to run next. Populated
automatically on authorisation of the record (new jobs) or on successful execution
of the job. NO date is populated for Daily jobs, as the jobs needs to be run daily.
User input is required for adhoc jobs.
3. Last Run Date is a No Input Field and is populated on successful execution of the
 job during COB.

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 12/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

TSA.SERVICE is the application where all services are defined and controlled by the
end user.

ID: The id of the service record must match a record in the BATCH application.
DESCRIPTION : This field holds the description of what the service is used for.
SERVER NAME : This field holds the IP address or the host name of the server where
the current service needs to be executed. This will be used on in a multi application
server architecture.
The whole idea behind a service is that you will have multiple copies of the process
running so that the load can be shared. How many such copies do you want running?
That is defined in the field WORK PROFILE. This field holds the ID of the record in
TSA.WORKLOAD.PROFILE application which defines the number of copies that will
actually execute.
USER : This field should hold a valid T24 user name, whose details are used to
update the audit fields of records that get created or updated by the service.
SERVICE CONTROL : This field can hold three values – AUTO, START and STOP.
STOP can be set in this field to stop the service when it is executing.
You will learn about the other fields in the next few slides.

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 13/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 14/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 15/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 16/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

1. REVIEW TIME :
The job of the tSM is to
Read the TSA.SERVICE records with SERVICE.CONTROL field set to START

Read the relevant TSA.WORKLOAD.PROFILE records

Check if the required number of agents are actually running
If yes, check to see if they are performing their job
If no, instruct the user to start the required number of agents
TIME OUT :
Every agent (tSA) is required to update the manager(tSM) that it is performing the task
assigned to it

The tSM is designed to wait for a stipulated amount

of time for each agent to report that it is alive and working

The tSM will term the agent as “dead”, if it doesn’t get a

reply within the stipulated time.

It will stop the tSA process at the operating system level (kill the process) and start a
substitute process

The time given for every agent to report to the tSM that it is alive and working is set in

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 17/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

the field TIME.OUT (Specify the value in the COB record)

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 18/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

What you see here is the TSM record in TSA.SERVICE application.

Description field holds the text that describes the TSA.SERVICE record

Server Name field holds the IP address or the host name of the server where this
service TSM needs to be executed.

There can be only one tSM per T24 application server. When MS (Multi
Server) product is installed, this field can be multi valued to include the ip of all
the servers involved in running COB

Work Profile field holds the ID of the TSA.WORKLOAD.PROFILE application which in

turn contains the number of agents required to run this service. For the record TSM,
the number of agents should always be 1. This field forms a multivalue set along with
Description and Server Name fields

User field holds a valid T24 user name. It has no significance for this record TSM. Has
significance for the record COB.

Service Control : It is the field that controls the starting and stopping of this service. If
set to START, T24 will allow us to start TSM by issuing the command START.TSM. To
stop the TSM, set this field to STOP.

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 19/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

This is the application used to specify the number of agents. The number of agents in
TSA.WORKLOAD.PROFILE can be set based on time. Agents can be
increased/decreased based on time (T24 application server time)

 Assume a scenario where in you know that the server will be busy at 11PM as that is
when transactions from an interface will be coming in. You may choose to reduce the
number of agents running COB during that period so that the server be used for the
interface as well. Define this in the TSA.WORKLOAD.PROFILE application.
TSA.WORKLOAD.PROFILE is the application which defines the number of tSAs
required. The ID of a record in this application can be any alphanumeric text.

The number of agents in TSA.WORKLOAD.PROFILE can be set based on time if

required.
TIME and AGENTS.REQUIRED : These fields are associated multi value set which
holds the specific time and the number of agents required at that point in time.

The number of agents that can run on server is directly proportional to the number of
processors available. Just because T24 supports multi threaded services doesn’t
mean you can start a 100 tSA’s in the background. It will kill the server. The thumb rule
to be followed is a maximum or 2 tSA’s per processor available.

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 20/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

In T24 multithreaded routines are executed by service agents.

This illustration will help you to understand how multiple agents help perform a job and
how failure of a single agent does not stop COB
Each server can have only 1 tSM. tSM, when started will launch the required number
of agents for that server 
Note that this tSM and the agents have been launched in Server 1. On Server 2,
another tSM has been launched, which internally launches the required number of
agents on that server 
Let us assume that all agents are helping in executing a particular job. Assume that
one of the tSAs on Server 1 is the one which has executed the .SELECT routine has
hence has populated the contents of the LIST file
 As you can see, all agents pick up IDs to be processed from the same LIST file thus
enabling to achieve multithreading
If you wish, you could add in one more server(s), start agents on that server and this
agent can also participate and process IDs from the LIST file
Even if one of the agents crash, since all other agents are active, they will continue to
pick up data from the LIST file.
This process will continue until the LIST file becomes empty.

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 21/34

 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

Parameter file
Has only one record  – ID is SYSTEM

Review Time Is used if the REVIEW.TIME field in the TSA.SERVICE record in not
specified. Default value is 60.

Death Watch Is used if the TIME.OUT field in the TSA.SERVICE record is not
specified. Default value is 300.

Highest Agent No input field. Updated by T24 with the number of agents running on
all T24 application servers put together 

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 22/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

You must first turn the service on using the SERVICE.CONTROL field in
TSA.SERVICE. This change must be authorised. You must remember that this action
does not start off the service in the background. Its only a flag to say that the service
will be picked up and executed.

You must then start the tSM program. This can be done only from the jBASE prompt.
This will cause all service records with either START or AUTO to be picked up to be
started.

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 23/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 24/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 25/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

Start the tSM by using START.TSM at the jBASE shell prompt. You have two options
when starting the tSM – to start it in DEBUG mode or to leave out the DEBUG option.

The DEBUG option allows you to manually start tSA’s to execute your service. In the
screen shot above, OFS.MESSAGE.SERVICE has one tSA assigned to it, but
SWIFT.OUT has two. How is this possible?

When defining a service in TSA.SERVICE, the field WORK.PROFILE links to an

application TSA.WORKLOAD.PROFILE where you can define how many tSA’s are
required. Each tSA represents one copy of your multi threaded service being
executed.

Now in the screen shot above, you must understand that the services have not been
started as yet.

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 26/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

 After the agents are assigned jobs, in DEBUG mode, type tSA <agent number> at the
 jBASE shell prompt to actually start the agents to the service. After the job is finished
successfully, a message ‘Agent Stopped’ will be displayed and the cursor will go back
to jBASE shell prompt.
When a service stops, the field SERVICE.CONTROL is set to STOP automatically.

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 27/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

Services can be configured as a periodic activity using the FREQUENCY field. This
field holds a value in the format
Date Time Frequency- where,
Date is the system date which is entered in T24 date format
Time is entered in the format HH:MM(T24 hour format)
Frequency is entered in the format 1D,2D etc.,
EXAMPLE : 20100215 14:00 1D

TSM would normally build the service profile only for the services which are set to
START or AUTO. But when the frequency is specified for the service and
SERVICE.CONTROL is set as ‘STOP’, the TSM would check whether the specified
frequency has been reached taking into account the time as well as frequency and
would start the service. When the service is stopped, the frequency would be cycled to

the next date.

be changed Thisfrequency
if the field is notisallowed
present.for an is
This AUTO service.
mostly Thearchiving.
using for service control cannot

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 28/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

You know tSM launches and controls the tSAs. How does an end user know what is
happening with the tSAs? Use the enquiry AGENT.STATUS

Agent ID is the allocated Agent Number for the service

T24.SESSION.NO is updated with a unique number that identifies every session in

T24. A number between 1 -99999 is allocated when a session is started in a port to
uniquely identify that particular session in T24(both for online and COB).
Note: This random number is generated using a routine called
EB.ALLOCATE.SESSION.NUMBER and is stored in a common variable called
C$T24.SESSION.NO. This helps in improving the monitoring capabilities of T24.
 A live file called T24.SESSION gets updated with record key being the
T24.SESSION.NO and contains information regarding the agent to which this session
number was assigned. A record in this application gets deleted, when the
corresponding process terminates(session expires).

Server Name is the name of the server where the agent is running. Note that details of
tSAs and tSMs across application servers will be updated here

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 29/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

Last Message is the message displayed by the agents as they are performing the
 jobs. The agent running tSM will not display any message as it is just monitoring
agents.

Como Name is the name of the log record ID that holds the log information of the
agent. These log records are stored in a directory called &COMO&. The contents of
these records cannot be viewed from browser. You will have to open these records at
the jBASE prompt. The log file name is in the format ‘tSA_<agent
number>_<date>_<time>’
LAST.MESSAGE is the message displayed by the agents as they are performing the
 jobs.
COMO.NAME holds the name of the log file that has the log information of the
particular agent.

JOB.PROGRESS holds the status of the jobs being performed.

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 30/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

COMO.NAME in AGENT.STATUS holds the name of the log file. Log files are stored
under a directory &COMO&. To view the log files use the command ‘LIST &COMO&’.
Use the command ‘JED &COMO& <Log file name>’ to view the contents of the log file.
If an agent is restarted, there will be two log files for that agent as the log file ID is
based on date and time. Log files do not get cleared automatically from the &COMO&.

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 31/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

1. FALSE – Single Threaded mode

2. FALSE – Each multi threaded routine in T24 must have a PGM.FILE entry with
TYPE ‘B’ for Batch
3. TRUE
4. FALSE – TSA.STATUS
5. TRUE
6. FALSE – TSA.STATUS

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 32/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 33/34

Services in T24
 

5/19/2018 10. Se r vic e s in T24 - slide pdf.c om

http://slide pdf.c om/re a de r/full/10-se r vic e s-in-t24 34/34

Services in T24