[T24] SERVICE vs PHANTOM

[Javed]

Guys,

I have some confusion around the subject, How to challenge the one in
favour of another, to more on effictiveness, performance and memory
management of the application and h/ ware level.

[Javed]

This is T24 question I did put [T24] at the begining of the message
but for some reason it is ignored in display... Ooops..

[Jim Idle]

There is in fact little difference as the only overhead for a Windows Service is the memory and code used to provide the service administration itself, which is not very much. Some situations mean that a service is more manageable than a phantom and others mean that a PHANTOM is easier. In the end, they both become background tasks. A service must create a registry set and must communicate via the Application Event log, which is difficult from jBC. A Phantom can just use PRINT so long as it has been given an output spooler job or something equivalent such as >myout.

On UNIX, just use cron rather than PH/Z/etc.

Jim

[John Watson]

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.

[Siddaiah BB]

Hi John,

 

which field in TSA.WORKLOAD.PROFILE will accept the start time for agents to start ?
 

Thanks & Regards

Siddaiah
 

[John Watson]

Errr,

TIME

Used in conjunction with the associated MV field AGENTS.REQUIRED.

[Sharath]

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

 

 

---

[Luis Lascano]

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

 

---