Siemens V 4.0 manual Cyclicorder, Taapplication, Cyclictime, Dynamicconnect

Configuration language

CYCLICORDER

The CYCLICORDER statement defines the maximum number of cyclical tasks permitted per

TA_APPLICATION.

The default value is CYCLICORDER(10).

The CYCLICORDER statement on system level applies to all hosts if there is no CYCLICORDER statement in the HOST statement.

The CYCLICORDER statement on host level applies accordingly to all TA applications if there is no CYCLICORDER statement in the TA_APPLICATION statement.

CYCLICTIME

The CYCLICTIME statement defines the interval for activation of the application-specific timer. The interval is specified by four values for days, hours, minutes and seconds. The default value is CYCLICTIME(0,0,0,0).

The CYCLICTIME statement on system level applies to all hosts if there is no CYCLICTIME statement in the HOST statement.

The CYCLICTIME statement on host level applies accordingly to all TA applications if there is no CYCLICTIME statement in the TA_APPLICATION statement.

DYNAMIC_CONNECT

ADYNAMIC_CONNECT statement on system level and on host level permits the definition of connections which are used by non-transaction-monitored clients to communicate with transaction-monitored T-ORB applications.

This statement can be used to define connections to several different T-ORB applications.

DYNAMIC_CONNECT((os,layer,number), ...)

The parameters os and layer refer to the OsLayerId in the TA_APPLICATION statement of the transaction-monitored T-ORB application to which connections are to be generated.

The parameter number defines the number of connections.

If there is no DYNAMIC_CONNECT statement for a host, then this host inherits the connec- tions specified at system level.

If this list is empty, this means that this host does not inherit any connections from the sys- tem level.

52 GINA V4.0 System Administrator Guide – September 2000