Section 5 - File Formats, Data Descriptions, MIBs, and System Processes Reference

Table 44 TM_MIB(5): T_CLIENT Class Definition Attribute Table

Attribute 1	Type	Permissions	Values	Default
TA_STATE(k)	string	R-XR-XR--	GET: "{ACT \| SUS \| DEA—>" SET: "{ACT \| SUS \| DEA}"	N/A N/A
TA_CLIENTID(*)	string	R--R--R--	string[1..78]	N/A
TA_CLTNAME(k)	string	R--R--R--	string[0..30]	N/A
TA_IDLETIME(k)	long	R--R--R--	0 <= num	N/A
TA_LMID(k)	string	R--R--R--	LMID	N/A
TA_PID(k)	long	R--R--R--	1 <= num	N/A
TA_CONTEXTID	long	R--R--R--	-2 <= num < 30,000	N/A
TA_SRVGRP(k)	string	R--R--R--	string[0..30]	N/A
TA_USRNAME(k)	string	R--R--R--	string[0..30]	N/A
TA_WSC(k)	string	R--R--R--	"{Y \| N}"	N/A
TA_WSH(k)	string	R--R--R--	"{Y \| N}"	N/A
TA_WSHCLIENTID(k)	string	R--R--R--	string[1..78]	N/A
TA_RELEASE	long	R--R--R--	0 <= num	N/A
TA_WSPROTO	long	R--R--R--	0 <= num	N/A
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_CMTRET	string	R--R--R--	"{COMPLETE \| LOGGED}"	N/A
TA_CURCONV	long	R--R--R--	0 <= num	N/A
TA_CURENCRYPTBIT	string	R--R-----	"{0 \| 40 \| 56 \| 128}" ²	N/A
TA_CURREQ	long	R--R--R--	0 <= num	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_NADDR	string	R--R--R--	string[1..256] ³	N/A
TA_NOTIFY	string	R--R--R--	"{DIPIN \| SIGNAL \| THREAD \| IGNORE}"	N/A
TA_NUMUNSOL	long	R--R--R--	0 <= num	N/A
TA_RPID	long	R--R--R--	1 <= num	N/A
TA_TIMELEFT	long	R--R--R--	0 <= num	N/A
TA_TIMESTART	long	R--R--R--	1 <= num	N/A
TA_TRANLEV	long	R--R--R--	0 <= num	N/A
(k)—GET key field (*)—GET/SET key, one or more required for SET operations

ACTive	T_CLIENT object active. This is not an indication of whether the client is idle or busy. A non 0 value retrieved for either the TA_CURCONV attribute or the TA_CURREQ attribute indicates a busy client.
SUSpended	T_CLIENT object active and suspended from making further service requests (tpcall() or tpacall()) and from initiating further conversations (tpconnect()). See SET SUSpended below for details. This state is ACTive equivalent for the purpose of determining permissions.
DEAd	T_CLIENT object 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 client notices the death and takes action to clean up the client's bulletin board resources. This state is ACTive equivalent for the purpose of determining permissions.

ACTive	Activate a SUSpended T_CLIENT object. State change allowed only when in the SUSpended state. Successful return leaves the object in the ACTive state.
unset	Modify an existing T_CLIENT object. This combination is allowed only when in the ACTive or SUSpended state. Successful return leaves the object state unchanged.
SUSpended	Suspend the T_CLIENT object from making service requests (tpcall() or tpacall()), initiating conversations (tpconnect()), beginning transactions (tpbegin()), and enqueuing new requests (tpenqueue()). Clients within a transaction will be permitted to make these calls until they abort or commit the current transaction, at which time they will become suspended. Invocations of these routines will result in a TPESYSTEM error return and a system log message being generated indicating the situation. State change allowed only when in the ACTive state. Successful return leaves the object in the SUSpended state.
DEAd	Abortively deactivate the T_CLIENT object. State change allowed only when in the ACTive or SUSpended state. The recommended method for deactivating clients is to first broadcast a warning message (tpbroadcast)), then to suspend them (see SET SUSpended above), and finally to abortively deactivate them by setting the state to DEAd. Successful return leaves the object in the DEAd state. Limitation: Workstation handlers (T_CLIENT:TA_WSH == Y) may not be set to a state of DEAd. The system may not be able to kill the client due to platform or signaling restrictions. In this case, a native client will be abortively terminated at its next access to ATMI, and a Workstation client's connection to a WSH will be preemptively torn down.