Regarding scheduling a service,
If I specify on my TSA.WORKLOAD.PROFILE, for an agent record REPORT.BATCH, a
time to run, say 7:00 AM and my system is at 22:00 hours. Then I run my COB
by starting tSM (or TSM), and starting COB service. It works fine but my
REPORT.BATCH service is also started in that moment.
So my question is, how can I tell TSM to run REPORT.BATCH service at time I
have specified on TSA.WORKLOAD.PROFILE?
DEMO-BANK TSA.SERVICE, SEE
SERVICE........... REPORT.BATCH
----------------------------------------------------------------------------
--
1 DESCRIPTION....... Generate reports
2. 1 SERVER.NAME.... t24server
3. 1 WORK.PROFILE... REPORT.BATCH
4 USER.............. TSA TSA
5 SERVICE.CONTROL... AUTO
7 TIME.OUT.......... 3200
DEMO-BANK TSA.WORKLOAD.PROFILE SEE
WORKLOAD.PROFILE.. REPORT.BATCH
----------------------------------------------------------------------------
--
1 DESCRIPTION....... Generate reports
2. 1 TIME........... 07:00
3. 1 AGENTS.REQUIRED 4
T24R4 -jBase 4.0
Regards,
Luis
_____
From: [email protected] [mailto:[email protected]] On Behalf Of
Sharath
Sent: 26 June, 2008 6:06 AM
To: [email protected]
Subject: [T24]: RE: SERVICE vs PHANTOM
Siddaiah
The filed TIME and AGENTS.REQUIRED are associated Multivalue fields.
If u specify time and the no of agents required , TSM will increase or
decrease the no of agents at the time specified.
Cheers
Sharath
_____
From: [email protected] [mailto:[email protected]] On Behalf Of
Siddaiah BB
Sent: Thursday, June 26, 2008 10:15 AM
To: [email protected]
Subject: Re: SERVICE vs PHANTOM
Hi John,
which field in TSA.WORKLOAD.PROFILE will accept the start time for agents to
start ?
Thanks & Regards
Siddaiah
On 6/26/08, John Watson <[email protected]> wrote:
This is an excellent example of the confusion that may arise if the
question is not specific and [T24] is not used.
Your question *may* be about the TSA.SERVICE functionality of T24, if
this is the case then basically the difference is that the tSM (T24
Service Manager) runs as a phantom and stops and starts functional
items defined in the TSA.SERVICE table - the tSA (T24 service Agents)
are then started and stopped as defined in the TSA.WORKLOAD.PROFILE
table
The advantage of this is that only 1 phantom is running continually;
the others are started and stopped as required.
A really good feature of the TSA.WORKLOAD.PROFILE is that you can set
a time (or multiple times) for a service to be started and the tSM
will only start the service at that time. You can also use this
functionality to scale up the number of agents of a service at peak
load times.
In summary the TSA.SERVICE functionality is far more flexible than
that provided by EB.PHANTOM and ultimately can result in a lower
system resource overhead
HTH.
John.
--~--~---------~--~----~------------~-------~--~----~
Please read the posting guidelines at:
http://groups.google.com/group/jBASE/web/Posting%20Guidelines
IMPORTANT: Type T24: at the start of the subject line for questions specific to
Globus/T24
To post, send email to [email protected]
To unsubscribe, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
-~----------~----~----~----~------~----~------~--~---
