Siemens V 4.0 manual PRIO7 ,TIMER ,EVENT ,CYCLIC ,PGWT Schedule, Priority, Medium, Low

Druck vom 24. 01.2001 17:00.29 torb-kon

Configuration language

PRIO(7 [,TIMER] [,EVENT] [,CYCLIC] [,PGWT] )

}

SCHEDULE

{

FUNCTION(<FunctionId>,<SyncPriority>,<AsyncPriority>,<Infostring>)

INSTMETHOD(<ClassId>,<InstMethodIdd>,<SyncPriority>,

<AsyncPriority>,<Infostring>)

CLASSMETHOD(<ClassId>,<ClassMethodId>,<SyncPriority>,

<AsyncPriority>,<Infostring>)

CLASS(<ClassId>,<Syncpriority>,<AsyncPriority>,<Infostring>)

}

}

The individual SYNC_PRIORITY, ASYN_PRIORITY and SCHEDULE blocks are described under the relevant keywords.

–The new PRIORITIES statement and the old PRIORITY and SCHEDULE statements are mutually exclusive, i. e. you can only assign one type of priority control to a

TA_APPLICATION.

–If you do not specify the PRIORITIES statement, priority control will be effected by means of the function for controlling processing of orders by restricting processes.

–You can specify the PRIORITIES statement at system, host and TA application level. The statement will be passed on from SYSTEM to HOST and from HOST to

TA_APPLICATION.

–Both the old priority control and the priority control described here can be used within a T-ORB configuration.

PRIORITY

TAC classes are controlled at the level of the specialist class, class method, instance method and function.

The PRIORITY statement defines three TAC classes with the priorities HIGH, MEDIUM and LOW. This statement summarizes a list of three entries:

HIGH ( tasks [, SYNC_WAIT] )

MEDIUM (		tasks	[,	SYNC_WAIT]	)
LOW	(	tasks	[,	SYNC_WAIT]	)

The parameter tasks specifies the maximum number of processes in the application which work concurrently with this TAC class. It depends on the statements MAX TASKS and

MAX TASKS-IN-PGWT.

GINA V4.0 System Administrator Guide – September 2000 59