Siemens V 4.0 User Manual

200

GINA V4.0 System Administrator Guide – September 2000

Administering GINA applications

The delivery of an alarm to a non-transaction-monitored application is broken up into two
parts. The partner is first informed of the event “Message n exists” via the auxiliary process
EventHandler, and then the message is collected.

The termination of the non-transaction-monitored partner or the EventHandler, for example
as a result of a power failure, can result in alarms being lost during delivery.

To prevent this, T-ORB provides a mechanism that monitors the delivery of alarms to non-
transaction-monitored partners.

T-ORB checks at certain intervals whether alarms that were announced to the partner via
the EventHandler have actually been collected. If this is not the case, T-ORB announces
them again.

The time intervals are defined by the

 CYCLE(d,h,m,s)

,

 CHECK(d,h,m,s)

and

CANCEL(d,h,m,s)

parameters in the

EVENTCONTROL

statement of the T-ORB generator

config

when the configuration is being created. For each transaction-monitored applica-

tion, the T-ORB generator

config

generates the

gina.config

file, in which the intervals

for the monitoring of alarms are stored (see Figure 41).

Figure 41    Time intervals for the monitoring of alarms

If these time intervals are to be changed while the transaction-monitored application is run-
ning, the

gina.config

file must be modified using a suitable editor (e.g.

vi

) and then the

DNEWCYCA

administration command activated using the administration facility (cf.

section 8.4.1 on page 199).

CTL2 0 0 10 0 100    // corresponds to CHECK(0,0,10,0)
CTL3 0 1 0 0         // corresponds to CHECK(0,1,0,0)
CTL4 2 0 0 0         // corresponds to CANCEL(2,0,0,0)