T_SERVER CLASS

Overview

The T_SERVER class represents configuration and run-time attributes of servers within an application. These attribute values identify and characterize configured servers as well as provide run-time tracking of statistics and resources associated with each server object.

Attribute Table

**T_SERVER Class Definition Attribute Table**
Attribute	Type	Permissions	Values	Default
`TA_SRVGRP( r )( * )`	string	ru-r--r--	string[1...30]	N/A
`TA_SRVID( r )( * )`	long	ru-r--r--	1 <= num < 30,001	N/A
`TA_SERVERNAME( k )( r )`	string	rw-r--r--	string[1...78]	N/A
`TA_GRPNO( k )`	long	r--r--r--	1 <= num < 30,000	N/A
`TA_STATE( k )`	string	rwxr-xr--	`GET`:"{`ACT\|INA\|MIG\|CLE\| RES\|SUS\|PAR\|DEA`}" SET:"{`NEW\|INV\|ACT\|INA \|DEA`}"	N/A N/A
`TA_BASESRVID`	long	r--r--r--	1 <= num < 30,001	N/A
`TA_CLOPT`	string	rwyr--r--	string[0...256]	"`-A`"
`TA_ENVFILE`	string	rwyr--r--	string[0...78]	""
`TA_GRACE`	long	rwyr--r--	0 <= num	`86,400`
`TA_MAXGEN`	long	rwyr--r--	1 <= num < 256	`1`
`TA_MAX`	long	rwxr--r--	1 <= num < 1,001	`1`
`TA_MIN`	long	rwyr--r--	1 <= num < 1,001	`1`
`TA_RCMD`	string	rwyr--r--	string[0...78]	""
`TA_RESTART`	string	rwyr--r--	"{`Y\|N`}"	`N`
`TA_SEQUENCE( k )`	long	rwxr--r--	1 <= num < 10,000	>= `10,000`
`TA_SYSTEM_ACCESS`	string	rwyr--r--	"{`FASTPATH\|PROTECTED`}"	(¹)
`TA_CONV( k )`	string	rw-r--r--	"{`Y\|N`}"	`N`
`TA_REPLYQ`	string	rw-r--r--	"{`Y\|N`}"	`N`
`TA_RPPERM`	long	rw-r--r--	0001 <= num <= 0777	(¹)
`TA_RQADDR( k )`	string	rw-r--r--	string[0...30]	"GRPNO.SRVID"
`TA_RQPERM`	long	rw-r--r--	0001 <= num <= 0777	(¹)
`TA_LMID( k )`	string	R--R--R--	LMID	N/A
`TA_GENERATION`	long	R--R--R--	1 <= num < 32K	N/A
`TA_PID( k )`	long	R--R--R--	1 <= num	N/A
`TA_RPID`	long	R--R--R--	1 <= num	N/A
`TA_RQID`	long	R--R--R--	1 <= num	N/A
`TA_TIMERESTART`	long	R--R--R--	1 <= num	N/A
`TA_TIMESTART`	long	R--R--R--	1 <= num	N/A
`T_SERVER Class: LOCAL Attributes`
`TA_NUMCONV`	long	R-XR-XR--	0 <= num	N/A
`TA_NUMDEQUEUE`	long	R-XR-XR--	0 <= num	N/A
`TA_NUMENQUEUE`	long	R-XR-XR--	0 <= num	N/A
`TA_NUMPOST`	long	R-XR-XR--	0 <= num	N/A
`TA_NUMREQ`	long	R-XR-XR--	0 <= num	N/A
`TA_NUMSUBSCRIBE`	long	R-XR-XR--	0 <= num	N/A
`TA_NUMTRAN`	long	R-XR-XR--	0 <= num	N/A
`TA_NUMTRANABT`	long	R-XR-XR--	0 <= num	N/A
`TA_NUMTRANCMT`	long	R-XR-XR--	0 <= num	N/A
`TA_TOTREQC`	long	R-XR-XR--	0 <= num	N/A
`TA_TOTWORKL`	long	R-XR-XR--	0 <= num	N/A
`TA_CLTLMID`	string	R--R--R--	LMID	N/A
`TA_CLTPID`	long	R--R--R--	1 <= num	N/A
`TA_CLTREPLY`	string	R--R--R--	"{`Y\|N`}"	N/A
`TA_CMTRET`	string	R--R--R--	"{`COMPLETE\|LOGGED`}"	N/A
`TA_CURCONV`	long	R--R--R--	0 <= num	N/A
`TA_CURREQ`	long	R--R--R--	0 <= num	N/A
`TA_CURRSERVICE`	string	R--R--R--	string[0...15]	N/A
`TA_CURTIME`	long	R--R--R--	1 <= num	N/A
`TA_LASTGRP`	long	R--R--R--	1 <= num < 30,000	N/A
`TA_SVCTIMEOUT`	long	R--R--R--	0 <= num	N/A
`TA_TIMELEFT`	long	R--R--R--	0 <= num	N/A
`TA_TRANLEV`	long	R--R--R--	0 <= num	N/A
( k ) - `GET` key field ( r ) - Required field for object creation (`SET TA_STATE NEW`) ( * ) - `GET/SET` key, one or more required for `SET` operations

¹Defaults to value set for this attribute in Class T_DOMAIN

Attribute Semantics

TA_SRVGRP: string[1...30]

Logical name of the server group. Server group names cannot contain an asterisk (*), comma, or colon.

TA_SRVID: 1 <= num < 30,001

Unique (within the server group) server identification number.

TA_SERVERNAME: string[1...78]

Name of the server executable file. The server identified by TA_SERVERNAME will run on the machine(s) identified by the T_GROUP:TA_LMID attribute for this server's server group. If a relative pathname is given, then the search for the executable file is done first in TA_APPDIR, then in TA_TUXDIR/bin, then in /bin and /usr/bin, and then in <path>, where <path> is the value of the first PATH= line appearing in the machine environment file, if one exists. Note that the attribute value returned for an active server will always be a full pathname. The values for TA_APPDIR and TA_TUXDIR are taken from the appropriate T_MACHINE object. See discussion of the T_MACHINE:TA_ENVFILE attribute for a more detailed discussion of how environment variables are handled.

TA_GRPNO: 1 <= num < 30,000

Group number associated with this server's group.

TA_BASESRVID: 1 <= num < 30,001

`ACTive`	`T_SERVER` object defined and active. This is not an indication of whether the server is idle or busy. An active server with a non 0-length `TA_CURRSERVICE` attribute should be interpreted as a busy server, that is, one that is processing a service request.
`INActive`	`T_SERVER` object defined and inactive.
`MIGrating`	`T_SERVER` object defined and currently in a state of migration to the server group's secondary logical machine. The secondary logical machine is the one listed in `T_GROUP`:`TA_LMID` attribute that does not match the `T_GROUP`:`TA_CURLMID` attribute. This state is `ACTive` equivalent for the purpose of determining permissions.
`CLEaning`	`T_SERVER` object defined and currently being cleaned up by the system after an abnormal death. Note that restartable servers may enter this state if they exceed `TA_MAXGEN` starts/restarts within their `TA_GRACE` period. This state is `ACTive` equivalent for the purpose of determining permissions.
`REStarting`	`T_SERVER` object defined and currently being restarted by the system after an abnormal death. This state is `ACTive` equivalent for the purpose of determining permissions.
`SUSpended`	`T_SERVER` object defined and currently suspended pending shutdown. This state is `ACTive` equivalent for the purpose of determining permissions.
`PARtitioned`	`T_SERVER` object defined and active; however, the machine where the server is running is currently partitioned from the `T_DOMAIN`:`TA_MASTER` site. This state is `ACTive` equivalent for the purpose of determining permissions.
`DEAd`	`T_SERVER` object defined, identified as active in the bulletin board, but currently not running due to an abnormal death. This state will exist only until the `BBL` local to the server notices the death and takes action (`REStarting\|CLEaning`). Note that this state will only be returned if the `MIB_LOCAL TA_FLAGS` value is specified and the machine where the server was running is reachable. This state is `ACTive` equivalent for the purpose of determining permissions.

`NEW`	Create `T_SERVER` object for application. State change allowed only when in the `INValid` state. Successful return leaves the object in the `INActive` state.
unset	Modify an existing `T_SERVER` object. This combination is allowed only when in the `ACTive` or `INActive` state. Successful return leaves the object state unchanged.
`INValid`	Delete `T_SERVER` object for application. State change allowed only when in the `INActive` state. Successful return leaves the object in the `INValid` state.
`ACTive`	Activate the `T_SERVER` object. State change allowed only when in the `INActive` state. (Servers in the `MIGrating` state must be restarted by setting the `T_GROUP`:`TA_STATE` to `ACTive`.) For the purpose of determining permissions for this state transition, the active object permissions are considered (that is, --x--x--x). Successful return leaves the object in the `ACTive` state. The `TMIB_NOTIFY TA_FLAG` value should be used when activating a server if status on the individual server is required.
`INActive`	Deactivate the `T_SERVER` object. State change allowed only when in the `ACTive` state. Successful return leaves the object in the `INActive` state. The `TMIB_NOTIFY TA_FLAG` value should be used when deactivating a server if status on the individual server is required.
`DEAd`	Deactivate the `T_SERVER` object by sending the server a `SIGTERM` signal followed by a `SIGKILL` signal if the server is still running after the appropriate timeout interval (see `TA_MIBTIMEOUT` in `MIB`(5)). Note that by default, a `SIGTERM` signal will cause the server to initiate orderly shutdown and the server will become inactive even if it is restartable. If a server is processing a long running service or has chosen to disable the `SIGTERM` signal, then `SIGKILL` may be used and will be treated by the system as an abnormal termination. State change allowed only when in the `ACTive` or `SUSpended` state. Successful return leaves the object in the `INActive`, `CLEaning` or `REStarting` state.