A_SER1[1].Services In T24-R10.01.pdf

1. Welcome to the “Service “Services s In T24” learning learning unit. This learni learning ng unit will will help you to un erstan tan t e concept o serv ces n .

SER1.Services In T24-R10.01

1

After completing this learning unit/course, you will be able to: •Differentiate between Phantoms and Services in T24 •Understand how a service works


2

Many software in the market, have processes that need to be run without user intervention. e proc proces esse ses s may may vary vary rom rom s mp e o s o ac ng up stor stor ca ata ata to c ear ear ng o temporary files or as important as interacting with interfaces to another system. These processes may be required executed once a day or may be required to be executed continuously for a period of time. T24 is no different and also has a number of these background processes. In the T24 releases prior to R05, these were called Phantoms. They were subroutines created in jBASE BASIC using T24 APIs if required and could be executed once or in an infinite loop until manually m anually stopped. This was handled via an application called EB.PHANTOM. This application was used to start and stop the processes. With the introduction of multi threaded t hreaded programming in release R05, this application can not be used if the background process is multi threaded. This application is not obsolete and can still be used if required.


3

1.Services are also background processes in T24. But they are multi threaded. 2.They too can be executed just once or in an infinite loop until manually stopped. 3.Services are controlled using an application called TSA.SERVICE


4

1 A service must be multi threaded, otherwise it must be run as a phantom. A multi threaded rout rout ne cons cons sts sts o t e o owng comp compon one ents. nts. rout rout ne to oa comm common on var a es used in the subroutine, a SELECT routine to select the Ids to be processed, a record routine which contains the logic to process each id selected and finally an insert file defined for the routine. 2 Each multi threaded routine in T24 must have a PGM. FILE entry with TYPE = B which stands for BATCH. 3 Each B type routine has an entry in the BATCH application, and a service is no different. diff erent. A service could be made up of one multi threaded routine or m ultiple routines that must be run in an order. You will use the BATCH record to define this order using the JOB field. The T he BATCH record that you will create will NOT have a BATCH.STAGE defined as this record must NOT be picked up during COB. 4 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 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.


In this learning unit, an existing service called BNK/SW IFT.OUT is used as an example. The screen s ots a ove s ow t e ent ca ca . an recor s. From the BATCH record, you can find out the actual name of the multi threaded routine and check it’s PGM.FILE entry


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

ID: The id of the service record must m ust match a record in the BATCH application. DESCRIPTION : This field holds the description of what the service is used for. SERVER NAME : This field f ield 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? T hat 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 t o stop the service when it is executing. You will learn about the other fields in the next few slides.


7

1. With the advent advent of multi threadin threading g in T24, two new programs programs (they (they are not not subroutines) subroutines) ave een co e to execute serv c es es. ey are t an t . 2. tSM is stands for T24 Service Manager and tSA stands for T24 Service Agent 3. The tSA program is in charge of actually executing the service(s). Each copy of the program executed, in turn executes one copy of the assigned service. 4. Since multiple copies of the tSA program can execute – only ONE tSM program executes to take care of the entire situation. You will now see how a service is executed so that this slide makes mak es more sense.


8

You must first turn the service on using the SERVICE.CONTROL field in TSA.SERVICE. s c ange mus must e aut or se . ou must remem er t at t s act on oes not start o t e service in the background. Its only a flag to say t hat 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 T his will cause all service records with either START or AUTO to be picked up to be started.


Start the tSM by using START.TSM START.T SM at the jBASE shell prompt. You have two options when start ng t e t – to start t n mo e or to eave out t e opt on. The DEBUG option allows you to manually m anually start tSA’s to execute your service. In the sc reen shot above, OFS.MESSAGE.SERVICE has one tSA assigned to it, but SW IFT.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.


10

num ber of tSAs required. TSA.WORKLOAD.PROFILE is the application which defines the number . 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 num ber 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 t o be followed is a maximum or 2 tSA’s per processor available.


11

After the agents are assigned jobs, in DEBUG mode, type t SA at the s e prompt to actua y start t e agents to t e serv ce. ter t e o s n s e 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. autom atically.


12

Services can be configured as a periodic activity using the FREQUENCY field. This field o s a va ue n t e o rm rmat Date Time Frequency Frequency-- where, 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 prof ile only for the services which are set to t o 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. This field is not allowed for an AUTO service. The service control cannot be changed if the frequency is present. This is mostly using for archiving.


1. To configure services as a periodic activity, input a date, time and frequency when the serv ce c e as to e starte n t e correspon ng . recor . ote t at t e serv ce ce control for the service PW.MAPPING is set to stop. The frequency configured for PW.MAPPING service is 20100216 11:35. The TSM has been started in interactive m ode. The time when the TSM is started is 11:32 on 16th Feb.


14

TSM builds the service profile for all services with service control set to ‘STO P’ and which ave a ‘ set. nce t e t me me as spec e n t e re requency e o t e serv ce ce has been reached, TSM automatically sets the service control for the service to ‘START’ and prompts the user to launch the required agents for the service(in DEBUG m ode). Once the service has stopped, the service control for the service is set back to ‘ST OP’ and the FREQUENCY gets cycled.


15

After the agents actually start performing the service, if you wish you have a look at the stat status us o t e age agent nts, s, an app app cat cat on can e use . you st t s app cat on, a . the services that are to be executed by the agents will be displayed. T he ID of the record in this will be the agent number.


16

You know tSM launches and controls the tSAs. How does an end user k now what is appen ng ng w t t e t s se t e enqu ry ry .

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 t o 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 c ommon 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

COB1.Close COB1.Close Of Business - Introductio Introduction-R10. n-R10.01 01

17

Slide 17 s1

The AGENT.STATUS enquiry output has been split into three screen shots as it elapses the screen. Some of the fields are explained in this slide and the remaining are explained in the next slide. salamelu, 2010/02/2 2010/02/23 3

Agent Status is the status of the agent. It can hold either of the three values.

RUNNING – Agent Agent performing performing the job



STOPPED – Agent has stopped properly. properly.



DEAD – Agent did not report report within the time given and hence the tSM has marked the agent as DEAD 

Process Id is the Operating system level process ID for the agent process that is running

perform ing at the moment. Note agent 1 is Current Service is the service the agent is performing performing the service TSM and the others are performing the service COB Next Service is the service the agent is supposed to perform next. W hile COB is running, if you wish to stop COB, set the field SERVICE.CONTROL to STOP for the record COB in the TSA.SERVICE file. Then, check the NEXT.SERVICE value for the agents running COB, it will be set to STOP STO P denoting that the agents needs to stop once they complete the current transaction Job Progress is the status of the j obs being performed. Details of the status is not in the scope of this learning unit.


18

Slide 18 s2

This slide is hidden in the slide show, it is present only for the notes page information salamelu, 2010/02/2 2010/02/23 3

Last Message is the message displayed by the agents as they are performing the jobs. T he agen agentt runn runn ng t w not not sp ay any any mess messag age e as t s ust ust mon mon tor tor ng agen agents ts.. 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___’

LAST.MESSAGE is the message displayed by the agents as they are perf orming the jobs. The agent running tSM will not display any m essage as it is just m onitoring agents. 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.


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


20

When multiple application servers are part on the T24 architecture, all processors can be ma e use o w en execut ng serv ces. ne t mus must e starte on eac server an t e tSA’s started appropriately. You must remember that data resides centrally – so in the TSA.SERVICE record, you will need to specify a workload profile for each server and also mention the server nam es in the corresponding multi-value fields.


21

1.

An activatio activation n file is a file in the the backend backend that contain contains s all the ID’s ID’s to be processed processed by the serv serv ce. ce. nce nce an s proc proces esse se rom rom t e act act vat vat on e, t s remo remove ve rom rom t ere ere

2.

Since we we have populat populated ed the file file with the ids ids that the servic service e needs to process, process, there there is no need for a SELECT routine separately

3.

For a service service to use an an activation activation file, file, it should should be be mentioned mentioned in the PGM.FILE PGM.FILE entry entry for the job that is running as a service. The T he field Activation File should be set to “YES” or the name of the activation file. If you choose the option as yes, then the name of the t he activation file will be F..LIST For eg: BNK/SWIFT.OUT, runs DE.OUTWARD job as a service. Now, as you can see in the screenshot, the field ACTIVATION.FILE ACTIVATION. FILE has been set to yes. Q. Based on what you learnt just now, what would be the name of the activation file? A. F.SWIFT.OUT.LIST (the BNK part is not included) NOTE: When you start a service by setting the SERVICE.CONTROL field to “START” in the TSA.SERVICE record of that service, you would expect the service to run once and then stop. This is not the case for f or services having activation files. When W hen a particular service has an activation file, it keeps running even if the SERVICE.CONTROL field is set to “START”.


22

1. 2. 3. 4. 5. 6.

FALS FALSE E – Sing Single le Thre Thread aded ed mode mode FALS FALSE E – Each Each ser serve verr shou should ld hav have e one one tSM tSM runn runnin ing g T RU E FAL FALSE – TSA TSA.STATU TATUS S T RU E FAL FALSE – TSA TSA.STATU TATUS S


23

You will now be able to: •Differentiate between Phantoms and Services •Explain the working of Services in T24


24


25

A_SER1[1].Services In T24-R10.01.pdf

Recommend Documents