File Formats, Data Descriptions, MIBs, and System Processes Reference
${TUXDIR}/include/tpadm.h
${TUXDIR}/udataobj/tpadm
tpacall(3c), tpalloc(3c), tpcall(3c), tpdequeue(3c), tpenqueue(3c), tpgetrply(3c), tprealloc(3c), Introduction to FML Functions, Fadd, Fadd32(3fml), Fchg, Fchg32(3fml), Ffind, Ffind32(3fml), MIB(5)
, TM_MIB(5)
Administering a BEA Tuxedo Application at Run Time
Setting Up a BEA Tuxedo Application
Programming a BEA Tuxedo ATMI Application Using C
Programming a BEA Tuxedo ATMI Application Using FML
EVENTS
—List of system-generated events
The System Event Monitor feature detects and reports certain predefined events, primarily failures, that a system operator should be aware of. Each event report is an FML32 buffer containing generic fields that describe the event plus other fields that describe the object associated with the event.
The BEA Tuxedo system periodically checks system capacities. If the system finds that a resource is exhausted or near capacity, it posts a system WARN
or ERROR
event. The system will continue to post these events until the condition subsides.
This reference page first defines the generic event reporting fields, and then lists all system events detected in the current BEA Tuxedo release. System event names begin with a dot ( .
).
Event reporting is currently limited to classes defined in TM_MIB(5)
and the T_DM_CONNECTION
class defined in
DM_MIB(5)
. Event reporting uses the MIB information base. See MIB(5)
and TM_MIB(5)
for a definition and the availability of "local attributes," and be aware that the availability of a local attribute depends on the state of communication within the application's network.
It is possible that the system will not post an event related to a system capacity limit (for example, .SysMachineFullMaxgtt
) if the condition only exists for a very short period of time.
A long integer containing the event detection time, in seconds, according to the clock on the machine where detection took place.
A long integer containing the event detection time, in microseconds, according to the clock on the machine where detection took place. While the units of this value will always be microseconds, the actual resolution depends on the underlying operating system and hardware.
The class of the object associated with the event. Depending on TA_CLASS
, the event notification buffer will contain additional fields specific to an object of this class.
INFO: .SysLicenseInfo: reached 100% of Tuxedo System Binary Licensed User Count, DBBL/BBL lockout canceled
.SysLicenseInfo: reached 90% of Tuxedo System Binary Licensed User Count
.SysLicenseInfo: reached 90% of Tuxedo System Binary Licensed User Count, DBBL/BBL lockout canceled
.SysLicenseInfo: reached below 90% of Tuxedo System Binary Licensed User Count, DBBL/BBL lockout canceled
INFO: .SysConnectionSuccess: Connection successful between %TA_DMLACCESSPOINT and %TA_DMRACCESSPOINT
INFO: .SysConnectionConfig: Configuration change for connection between %TA_DMLACCESSPOINT and %TA_DMRACCESSPOINT
ERROR: .SysServerMaxgen: %TA_SERVERNAME, group %TA_SRVGRP, id %TA_SRVID server exceeded MAXGEN restart limit
EVENT_MIB
—Management Information Base for EventBroker
#include <tpadm.h>
#include <fml32.h>
#include <evt_mib.h>
The BEA Tuxedo EventBroker MIB defines the set of classes through which the EventBroker can be managed.
EVENT_MIB
(5) should be used in combination with the generic MIB reference page, MIB(5)
, to format administrative requests and interpret administrative replies. Requests formatted as described in MIB(5)
and a component MIB reference page may be used to request an administrative service using any one of a number of existing ATMI interfaces in an active application. For additional information pertaining to all EVENT_MIB(5)
class definitions, see EVENT_MIB(5) Additional Information.
EVENT_MIB
consists of the following classes.
Each object in these classes represents a single subscription request.
The pattern expression of TA_EVENT_EXPR
in each class determines whether it is a SYSTEM EVENT
request or an USER EVENT
request. The determination on which one to query is made as follows:
TA_EVENT_EXPR
or TA_EVENT_SERVER
specified will always go to the SYSTEM EVENT
request and will not return USER
EVENT
request.TA_EVENT_EXPR
specified but not TA_EVENT_SERVER
will go to the SYSTEM EVENT
request if the expressions starts with "\.".
Otherwise, it will go to the USER EVENT
request.TA_EVENT_SERVER
specified with a value of "SYSTEM"
will go to the SYSTEM EVENT
request. A value of "USER"
will direct the request to the USER EVENT
.The field table for the attributes described in this reference page is found in the file udataobj/evt_mib
(relative to the root directory of the BEA Tuxedo system software). The directory ${TUXDIR}/udataobj
should be included by the application in the colon-separated list specified by the FLDTBLDIR32
environment variable and the field table name evt_mib
should be included in the comma-separated list specified by the FIELDTBLS32
environment variable.